1. Configuring Weblogic Server
  2. Tuning
  3. JVM Tuning

JVM Tuning

This section of the document provides JVM optimization for Oracle Banking Payments Solution.

Figure 5-1 JVM


JVM

The JAVA minimum and maximum heap size needs to be reset for 32 and 64 bit environments. Both the minimum and maximum heap size is set to 1.5GB and 4GB in 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 where as 32bit throws an error.

How to modify the JVM heap parameters?

To change the JVM heap parameters modify setDomainEnv.sh under domain FCUBSCL in both servers. This file is located at

“$WL_HOME/user_projects/domains/$WLS_DOMAIN/bin” in both the servers.

Use below USER_ MEM_ARGS variable to override the standard memory arguments passed to java for SUN JDK.

32 bit JDK

It is strictly not recommended to use a 32 bit JDK version because this have a limitation of maximum heap size setting to 4 GB only. This restricts the application scalability.

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.parser s.XML11Configuration -Dweblogic.threadpool.MinPoolSize=100 - Dweblogic.threadpool.MaxPoolSize=100 –Xms8g –Xmx8g -server -d64 - XX:+UseParallelOldGC -XX:ParallelGCThreads=4" export USER_MEM_ARGS

Note:

Take a backup of the files before modifying the same.

Parent topic: Tuning