Scheduler shuts Down with error "CAUAJM_E_10906 Detected critical dual event synchronization deadlock. Detailed information below. Shutting down."
Article ID: 182884
Updated On:
Products
Issue/Introduction
Autosys Scheduler starts up fine but while processing events, it shuts down. Below error is seen in the event_demon logs:
CAUAJM_E_10906 Detected critical dual event synchronization deadlock. Detailed information below. Shutting down.
Environment
Workload Automation AE (AutoSys)
Cause
The critical dual event synchronization deadlock occurs typically when the scheduler experiences a flaw while trying to fetch the same events in both of the two AutoSys databases. If after several iterations of trying the scheduler is unable to fetch synchronized events from both databases after resorting the events it fetches, then the scheduler needs to shut down.
Typically, as the scheduler run jobs, it generates events in both databases. The issue is unlikely to occur until a large number of events are sent manually during a time of high scheduler activity. In the case of manually sent events, the application server competes with the scheduler to add events into both databases. This can cause events to be written in the wrong order in both databases. Typically, the scheduler can synchronize events whose order differs in both databases. But if for unknown reasons it cannot re-sync.
Resolution
Resync the databases using autobcp and restart scheduler
Feedback
