EM 13c : Agent Generates Many Incidents with "Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskSchedule"
(Doc ID 2108408.1)
Last updated on SEPTEMBER 13, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.1.0.0.0 to 13.1.0.0.0 [Release 13c]Information in this document applies to any platform.
Symptoms
The Enterprise Manager (EM) 13c Cloud Control Agent generates frequent 'DispatchingTaskScheduler' alerts,
Email notification:
Host=<HOSTNAME>.<DOMAIN_NAME>
Target type=Agent
Target name=<HOSTNAME>.<DOMAIN_NAME>:3872
Incident creation time=Jan 31, 2016 7:23:21 AM EST
Last updated time=Jan 31, 2016 7:23:43 AM EST
Message=Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071.
Severity=Critical
Target type=Agent
Target name=<HOSTNAME>.<DOMAIN_NAME>:3872
Incident creation time=Jan 31, 2016 7:23:21 AM EST
Last updated time=Jan 31, 2016 7:23:43 AM EST
Message=Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071.
Severity=Critical
When these alerts are triggered, incidents are generated under '[Agent_Instance_Home]/diag/ofm/emagent/emagent/incident/'
The readme.txt file from the incident shows the below stack:
java.lang.Throwable: Duplicate Scheduled Tasks
at oracle.sysman.gcagent.tmmain.diag.DiagManager.createIncident(DiagManager.java:770)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler.checkForDuplicateScheduledTasks(DispatchingTaskScheduler.java:1071)
at oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc$SystemMonitoring$CheckForDuplicateScheduledTasksRunnable.run(TMComponentSvc.java:1998)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at oracle.sysman.gcagent.util.system.GCAThread$RunnableWrapper.run(GCAThread.java:198)
at java.lang.Thread.run(Thread.java:745)
at oracle.sysman.gcagent.tmmain.diag.DiagManager.createIncident(DiagManager.java:770)
at oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler.checkForDuplicateScheduledTasks(DispatchingTaskScheduler.java:1071)
at oracle.sysman.gcagent.tmmain.lifecycle.TMComponentSvc$SystemMonitoring$CheckForDuplicateScheduledTasksRunnable.run(TMComponentSvc.java:1998)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at oracle.sysman.gcagent.util.system.GCAThread$RunnableWrapper.run(GCAThread.java:198)
at java.lang.Thread.run(Thread.java:745)
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |