JVM Parameters For WebLogic Server With ASAP 7.3.x (Doc ID 2288281.1)

Last updated on AUGUST 11, 2017

Applies to:

Oracle Communications ASAP - Version 7.3.0.0.0 and later
Information in this document applies to any platform.

Goal

We have recently moved part of our functionality from ASAP 7.0.2 to ASAP 7.3.0 Patch 1.
When we observe the permanent generation usage in the environment, we noticed that PermGen usage in WebLogic is reaching above 90%.

Environment Details:

  ASAP Version : ASAP 7.3.0 Patch 1
  JDK Version : jdk1.7.0_97_b33(64 bit)
  Weblogic Server : 12.1.3.0.0
  OS : Redhat Enterprise Linux 6.8

We are using G1GC algorithm.

Are there any known issues with respect to G1GC algorithm with JVM{jdk1.7.0_97_b33(64 bit)} version we are using?

We applied JVM parameter changes as follows: 

1) This JVM configuration caused WLS/OCA not responding even when there is less traffic(we were sanity testing with 1-2 work orders)
-Xms2048m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:MaxNewSize=768m -XX:NewSize=768m

2) This JVM configuration caused WLS/OCA not responding. We could process around 300 work orders then we started seeing the issue.
-Xms2048m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseG1GC

3) Finally, we are currently using the below setting for the last 24 hours.
-Xms2048m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+UseG1GC
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms