Migrated OC4J to WLS 10.3.5 application running slow
(Doc ID 1377423.1)
Last updated on OCTOBER 09, 2020
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
The architecture used on the environment:
Oracle WebTier (OHS Apache 10.1.3.3 + WebCache)
WLS Proxy Plugin
*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 HOST_NAME 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
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 the script.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document