My Oracle Support Banner

EM 13c: Agent Monitoring oam_server Targets Consuming High CPU Usage (Doc ID 2317721.1)

Last updated on JUNE 18, 2018

Applies to:

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


EM 13c Agent monitoring oracle_oam targets consuming High CPU.

Thread dumps during the high CPU time shows the following stack:

"GC.Executor.4 (oracle_oam:/oam_domain/oam_server2/oam_server( (oracle_oam:/oam_domain/ksoam_domain/oam_server2/oam_server(" prio=10 tid=0x00007f2fdcca1800 nid=0x5e1f waiting on condition [0x00007f2fe4323000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000f42fe8c0> (a java.util.concurrent.FutureTask)
at java.util.concurrent.locks.LockSupport.park(
at java.util.concurrent.FutureTask.awaitDone(
at java.util.concurrent.FutureTask.get(
at oracle.sysman.gcagent.addon.fetchlet.logmgmt.workerthreads.LogExecutorService.startProcess(
at oracle.sysman.gcagent.addon.fetchlet.logmgmt.LogMonitoringFetchletWrapper.getMetric(

<AGENT_INST_HOME>/sysman/log/gcagent.log file shows that agent is timing out while collecting the oracle_oam target's oam_log_file_monitoring metric.


To view full details, 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 a vibrant support community of peers and Oracle experts.