EM 12c: Enterprise Manager 12c Cloud Control Agent is Restarting Frequently due to Error: java.lang.OutOfMemoryError: Java heap space (Doc ID 2116481.1)

Last updated on SEPTEMBER 16, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.4.0 to 12.1.0.5.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

EM 12.1.0.4 agent is crashing / re-starting frequently.

-  The <agent_inst>/sysman/log/gcagent.log reports:

<timestamp> [1:main] ERROR - agent main threw an error java.lang.OutOfMemoryError: Java heap space at java.util.Formatter.parse(Formatter.java:2480) at java.util.Formatter.format(Formatter.java:2414) at java.util.Formatter.format(Formatter.java:2367) at java.lang.String.format(String.java:2769) at oracle.sysman.gcagent.tmmain.AgentStatus.writeStatusMessage(AgentStatus.java:117) at oracle.sysman.gcagent.tmmain.TMMain.writeCurrentStatus(TMMain.java:649) at oracle.sysman.gcagent.tmmain.TMMain.waitForSignal(TMMain.java:682) at oracle.sysman.gcagent.tmmain.TMMain.agentMain(TMMain.java:597) at oracle.sysman.gcagent.tmmain.TMMain.main(TMMain.java:546) 2016-02-24 10:18:48,858 [164:CDEB16E1:GC.SysExecutor.9 (Ping OMS)] INFO - attempting another heartbeat 2016-02-24 10:18:57,568 [1:main] ERROR - Critical error: java.lang.OutOfMemoryError: Java heap space
 

The <agent_inst>/sysman/log/emagent.nohup shows:

inMemoryLoggingSize=5242880
_SchedulePersistTimer=30
MaxThreads=10
agentJavaDefines=-Xmx844M -XX:MaxPermSize=96M
SchedulerRandomSpreadMins=5
UploadMaxNumberXML=5000
UploadMaxMegaBytesXML=50.0
Auto tuning was successful
----- Tue Mar 1 23:03:08 2016::26712::Finished auto tuning the agent at time Tue Mar 1 23:03:08 2016 -----
----- Tue Mar 1 23:03:08 2016::26712::Launching the JVM with following options: -Xmx768M -XX:MaxPermSize=256M -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- Tue Mar 1 23:03:08 2016::26712::Agent Launched with PID 36792 at time Tue Mar 1 23:03:08 2016 -----
----- Tue Mar 1 23:03:08 2016::36792::Execing EMAgent process is taking longer than expected 120 secs -----
----- Tue Mar 1 23:03:08 2016::36792::Time elapsed between Launch of Watchdog process and execing EMAgent is 32230 secs -----
2016-03-01 23:03:08,572 [1:main] WARN - Missing filename for log handler 'wsm'
2016-03-01 23:03:08,579 [1:main] WARN - Missing filename for log handler 'opss'
2016-03-01 23:03:08,580 [1:main] WARN - Missing filename for log handler 'opsscfg'
Agent is going down due to an OutOfMemoryError
----- Wed Mar 2 01:16:20 2016::26712::Checking status of EMAgent : 36792 -----
---Wed Mar 2 01:16:26 2016Detected a gap of (209063) that is greater than the allowed tolerance of (150000)
----- Wed Mar 2 01:16:27 2016::26712::Checking status of EMAgent : 36792 -----
----- Wed Mar 2 01:16:27 2016::26712::EMAgent exited at Wed Mar 2 01:16:27 2016 with return value 57. -----
----- Wed Mar 2 01:16:27 2016::26712::EMAgent will be restarted because of an Out of Memory Exception. -----
----- Wed Mar 2 01:16:27 2016::26712::writeAbnormalExitTimestampToAgntStmp: exitCause=OOM : restartRequired=1 -----
----- Wed Mar 2 01:16:27 2016::26712::Restarting EMAgent. ----------

 

 

Changes

 

Cause

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