Tuning Third-Party Containers

For 32-bit Sun JRE 1.5 on Solaris 10 (both Sparc and x86), the following JVM options can be used as an example. The actual heap sizes should be adjusted based on the available physical memory, other processes running and the presence of any other active web applications running in the same JVM as OpenSSO.

-server
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-Xms3136M 
-Xmx3136M
-XX:NewSize=392M
-XX:MaxNewSize=392M
-Xss128k

If JRE 1.6 is used, the following diagnostic JVM options can be added:

• -XX:+HeapDumpOnOutOfMemoryError

• -XX:+PrintConcurrentLocks

For more information on troubleshooting JRE 6 deployment, see “Troubleshooting Java SE 6 Deployment”.

For more efficient garbage collection processing of soft reference objects, add the -XX:+DoEscapeAnalysis JVM option which is available with JDK 1.6.0_14 and later versions. To improve the performance of 64–bit JRE, add the -XX:+UseCompressedOops JVM option which is available with JDK 1.6.0_14 and later versions. This option compresses object references to 32 bits of the 64–bit JRE heap if the total heap is less than 32GB in size, reducing the amount of data that the HotSpot garbage collection engine must process.

The Escape analysis-based optimization option -XX:+DoEscapeAnalysis is disabled in JDK 1.6.0_18. This option will be restored in a future Java SE 6 update. For more information on these two options, see “Java SE 6 Update Release Notes.”

For WebLogic Application Server, increase the MaxPermSize from the default value of 128m to 256m in setDomainEnv.sh as shown below:

"if [ "${JAVA_VENDOR}" = "Sun" ] ; then
       MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} -XX:MaxPermSize=256m"
       export MEM_ARGS
fi"

Otherwise, WebLogic Application Server may not start up with OpenSSO Enterprise 8.0 deployed.