IBM Heap Analyser - Java.lang.OutofMemoryError: Java heap space

IBM Heap Analyser -

I started getting "Java.lang.OutofMemoryError: Java heap space" when trying to read a heapdump file using the heap analyser. used the below on a windows 2008r2 server where I had 64bit java  installed. specified the initial and max heapsize and it started working.

D:\Program Files\Java\jdk1.7.0_25\bin>java -Xms2g -Xmx6g -jar d:\temp\ha450.jar

Siteminder r6 - separate keystore from policy store

We have r6sp5 siteminder environment which we are looking to parallel upgrade to r12sp3 soon. below are some detailed steps how to separate the KeyStore from the policy store in a r6sp5 environment. The siteminder documentation is very vague in its description of how to do this.

***************

1.Take the backup of existing keys for the policy server:
smobjexport.exe -dsiteminder -wP@55word -okey.smdif -x -v

2. Create a new LDAP Key Store instance in your directory server.
3. Now open the Siteminder smconsole and go to the data tab-> Select Key Store, then uncheck the option-Use Policy Store Database. And fill the details for your newly created Keystore (like IP: Port, username, password and root DN) in this Keystore tab. After this click OK.

4. Open Command Prompt, go to /bin and perform the following command :-
smldapsetup ldgen -fnewkeystoreschema.txt -v -k1
This will create a schema file for your new keystore instance

6. Also at the same location run the following command :-
smldapsetup ldmod -fnewkeystoreschema.txt -v -k1
This will create the Schema in your New LDAP keystore from this schema file

7. run
smobjimport.exe -dsiteminder -wP@55word -ikey.smdif -k -v

8. Now we are done with the creation of new keystore. Start the policy server and check the logs.
*****************

Slow Performance on Windows 7 while browsing IIS Apps - AutoTuning

We recently migrated all our IIS applications from old Windows 2000 Servers to Windows 2008. It was not a smooth ride but we did manage to get 99% of them into the new servers. There were ofcourse some apps with exe's that were not supported or cannot move to x64. Parallely most of our users were being upgraded from their Windows XP to Windows 7 PC/Laptops.

We found that users connecting from Win7 to IIS face performance problems in the corporate network. The performance was so bad that it took 20+ seconds to display a single page. We also found that the sites worked perfectly when users connected to IIS via a reverse proxy or when they connected using a Windows XP machine.

So the problem was with Windows 7 and by trial and error method we found that AutoTuning was the issue. I think Microsoft enabled AutoTuning by default in Windows 7 and somehow that setting is not compatible with our network gear.

To disable AutoTuning on a Windows7 Machine.
1) open command prompt as Administrator
search for cmd in ‘Start’ and press CTRL+SHIFT+ENTER instead of just enter.
2) paste the below command to get Ok.
netsh interface tcp set global autotuning=disabled

Restored Windows 2003 Server - IIS would not start

The IIS Admin Service service terminated with service-specific error 2148073483 (0x8009000B).

During a DR Drill when we recovered a Windows 2003 server, IIS would not start. The IIS Admin Service and WWW Service stopped and were giving the above error. To correct this reinstall did not work and it further corrupted everything.

Then we did a restore of SystemState and it resolved the issue.