EM 13c: Agent is Consuming High CPU and gcagent.log Reports Error "java.sql.SQLException: The connection is closed: The connection is closed"
(Doc ID 2478680.1)
Last updated on SEPTEMBER 24, 2019
Applies to:Enterprise Manager Base Platform - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 13c]
Information in this document applies to any platform.
EM Agent 13.2 or 13.3 consuming high CPU.
<Agent Instance Base>/agent_inst/sysman/log/gcagent.log file reports following errors:
Also, if a thread dump is taken on the EM agent process, a huge number of "Timer-" threads are observed (which are increasing over time and never getting closed/finished). Example:
jstack <Agent PID>|grep "Timer-"|wc -l
Note: as a rule of thumb, the number of "Timer-" threads should be pretty constant over time, less than 50, however this is an approximate value as it depends on the number of targets, monitoring settings, jobs executed and many other factors. The key factor is to see an approximately constant number of such threads over time (days).
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