Cisco Bug: CSCuo85151 - PI: Health monitoring jobs stuck in the scheduled state
Last Modified
Feb 15, 2018
Products (1)
- Cisco Prime Infrastructure
Known Affected Releases
2.0(0.0.294)
Description (partial)
Symptom: Health monitoring jobs stuck in the scheduled state: Following messages are available in the jobManager.log: [2014-04-28 15:29:41,957] [myScheduler_Worker-5] [LoggingTriggerHistoryPlugin] [INFO ] - Trigger DEFAULT.Trigger_CollectionPlanPushJob###PushCollectionPlanToDA completed firing job DEFAULT.CollectionPlanPushJob###PushCollectionPlanToDA at 15:29:41 04/28/2014 with resulting trigger instruction code: DO NOTHING [2014-04-28 15:30:01,163] [myScheduler_Worker-3] [LoggingTriggerHistoryPlugin] [INFO ] - Trigger DEFAULT.Trigger_PollerJob###SAM_Poller_11700_1_CPU_168013170 fired job DEFAULT.PollerJob###SAM_Poller_11700_1_CPU_168013170 at: 15:30:01 04/28/2014 [2014-04-28 15:30:01,165] [myScheduler_Worker-3] [JobRunShell] [ERROR] - Job DEFAULT.PollerJob###SAM_Poller_11700_1_CPU_168013170 threw an unhandled Exception: org.springframework.core.task.TaskRejectedException: Executor [java.util.concurrent.ThreadPoolExecutor@c3dfdd6] did not accept task: com.cisco.xmp.jobmanager.common.JobProcessor@53855d86 Conditions: Unknown
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Status
- Severity
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases