Migrated OC4J to WLS 10.3.5 application running slow

(Doc ID 1377423.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version 10.3.5 and later
Information in this document applies to any platform.


After migrating a custom Spring J2EE Application has been from OC4J to WebLogic Server, the performance of the application decreases dramatically.

To make a proper comparison:

OC4J  :   1 seconds
WLS   :   6 seconds

Architecture used on the environment:

        Citrix Netscaler HW Load Balancer
Oracle WebTier (OHS Apache + WebCache)
         WLS Proxy Plugin
        SSO Plugin
         *WLS Back-End

*For this specific case, the WebLogic Backend description is the following.

1. 36 Managed servers, distributed in 18 clusters. Each cluster is composed by two managed servers. There are 2 physical machines, with the following specs:
SunOS mia-slz-p04 5.10 Generic_144489-12 i86pc i386 i86pc (Solaris 10) 2 Cores per Machine. Memory size: 65526 Megabytes

2. Each and every managed server has the following set up:
Memory set up: JAVA Memory arguments: -Xms1512m -Xmx1512m -Xmn512m -XX:+AggressiveOpts -XX:+UseParallelGC -XX:ParallelGCThreads=16 -XX:PermSize=256m -XX:MaxPermSize=768m

3. JVM:
java version "1.6.0_25"
Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.0-b11, mixed mode)

-Xms1512m -Xmx1512m -Xmn512m -XX:+AggressiveOpts -XX:+UseParallelGC -XX:ParallelGCThreads=16 -XX:PermSize=256m -XX:MaxPermSize=768m

4. Node Manager used to bring up managed servers.
5. Admin server goes up by script.


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