4.2 JVM Tuning

This topic provides information on JVM optimization for Oracle Universal Banking Solution.

The JAVA minimum and maximum heap size need to be reset for 32 and 64-bit environments. Both the minimum and maximum heap sizes are set to 1.5GB and 4GB in the case of 32-bit and 64-bit environments respectively.

How to find whether the JVM is 32bit or 64bit?

Go to $JAVA_HOME/bin directory. Check java version using command ./java –d64 –version 64 bit JVM shows the version details whereas 32bit throws an error.

How to modify the JVM heap parameters?

To change the JVM heap parameters create a file setUserOverrides.sh under domain FCUBSCL in both servers. This file should be created in $WL_HOME/user_projects/domains/$WLS_DOMAIN/bin in both the servers. Paste below the contents of the USER_MEM_ARGS variable accordingly to override the standard memory arguments passed to java for SUN JDK.

32 bit JDK

USER_MEM_ARGS="-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XML11Configuration -Dweblogic.threadpool.MinPoolSize=100 -Dweblogic.threadpool.MaxPoolSize=100 –Xms1536M –Xmx1536M -XX:MaxPermSize=256m -server -XX:+UseParallelOldGC -XX:ParallelGCThreads=4"
export USER_MEM_ARGS

64 bit JDK

USER_MEM_ARGS="-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.a
pache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XML11Configuration -Dweblogic.threadpool.MinPoolSize=100 -Dweblogic.threadpool.MaxPoolSize=100 –Xms8g –Xmx8g –Xmn4g -server -XX:+UseParallelOldGC -XX:ParallelGCThreads=4"
export USER_MEM_ARGS

Note:

Take a backup of this files before modifying them same.