My Oracle Support Banner

EM 13c Agent Crashes with Agent is going down due to an OutOfMemoryError (Doc ID 2417792.1)

Last updated on JULY 19, 2020

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.


EM 13c Agent crashes with "Agent is going down due to an OutOfMemoryError".

AGENT_INST_HOME/sysman/log/emagent.nohup reports:

Agent is going down due to an OutOfMemoryError
----- 2018-06-20 15:06:12,864::130355::Checking status of EMAgent : 137773 -----
----- 2018-06-20 15:06:12,864::130355::EMAgent exited at 2018-06-20 15:06:12,864 with return value 57. -----
----- 2018-06-20 15:06:12,864::130355::EMAgent will be restarted because of an Out of Memory Exception. -----
----- 2018-06-20 15:06:12,864::130355::EMAgent is Thrashing. Exiting loop. -----
----- 2018-06-20 15:06:12,864::130355::Commiting Process death. -----
----- 2018-06-20 15:06:12,864::130355::writeAbnormalExitTimestampToAgntStmp: exitCause=OOM : restartRequired=0 -----
----- 2018-06-20 15:06:12,864::130355::Exited due to Thrash. -----

AGENT_INST_HOME/sysman/log/gcagent.log file reports:

java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(
at java.lang.AbstractStringBuilder.ensureCapacityInternal(
at java.lang.AbstractStringBuilder.append(
at java.lang.StringBuilder.append(

Generated file shows memory leak (Need to analyze with any HeapDump Analyzer) as follows:

"" loaded by "sun.misc.Launcher$AppClassLoader @ 0xb555bb38" occupies 255,861,144 (88.03%) bytes. The memory is accumulated in one instance of "char[]" loaded by "<system class loader>".

<Java Local> oracle.sysman.gcagent.util.system.GCAThread @ 0xb68cfc90 GC.Executor.8


( Thread




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.