Last updated on OCTOBER 20, 2017
Applies to:Oracle Configurator - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 26-JAN-2015***
Oracle Configurator performs poorly (Java: Out of memory)
When using the Oracle Configurator observing strange behaviour of the oacore java process.
Customer has defined 5 oacore java processes in the OC4J container with a max heap space of 2GB (the jdk is 32-bit).
The load increases when the Java process consumes 100% CPU and is finally killed by opmn.
In the oacorestd.err is seen: java.lang.OutOfMemoryError: GC overhead limit exceeded
Tried adding the paramter -XX:-UseGCOverheadLimit to startup, and paramter
-XX:-UseGCOverheadLimit , Both didnt help
The CPU still shows at100%
(Five oacore JVMs, 1 forms JVM and one oafm JVM (was earlier onlyl 2 oacore
JVM's). 24 cores.
and EBS users Average 45.84 Max 108
Concurrent Requests Average 47.31 Max 140
MaxPermSize is set to 512MB
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