Server routines UPDJP and LOEBJP causing deadlocks

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• Automic SaaS

Issue/Introduction

This issue occurs due to a deadlock between the UPDJP and LOEBJP routines within a Top Workflow (WF) and a Child WF structure.

In certain cases, the Child WF may become blocked, and when an operator manually unblocks it, both routines can run in parallel. The issue arises because:

• UPDJP correctly locks the parent execution handle (EH) first, then its own.
• LOEBJP, however, locks its own EH first, performs extensive processing, and then attempts to lock the parent EH—which may already be locked by UPDJP.

If both routines execute at the same time, this mismatch in lock handling can lead to a deadlock, potentially causing the system to freeze until manual intervention is performed.

Below error messages can be seen in the logs:

U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: f6bd40  DB-HDBC: fe63b0
U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'
U00003592 UCUDB - Status: '' Native error: '60' Msg: 'ORA-00060: deadlock detected while waiting for resource'
U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages.
U00003524 UCUDB: ===> Time critical DB call!       OPC: 'SLCU' time: '11:178.789.999'
U00003434 Server routine  'JPEXEC_R/LOEBJP' required '1' minutes and '10,832' seconds for processing.

U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: f6bd40  DB-HDBC: fe63b0
U00003591 UCUDB - DB error info: OPC: 'OCIStmtExecute' Return code: 'ERROR'
U00003592 UCUDB - Status: '' Native error: '60' Msg: 'ORA-00060: deadlock detected while waiting for resource'
U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages.
U00003524 UCUDB: ===> Time critical DB call!       OPC: 'SLCU' time: '11:761.701.000'
U00003434 Server routine  'JPEXEC_R/UPDJP' required '0' minutes and '21,452' seconds for processing.

Note: The likelihood of this occurring depends on timing and resource conditions.

Environment

Release: 21.0.x

Component: Automation Engine

Cause

The issue has been confirmed to be a bug by our Dev team.

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Automation Engine

Automation.Engine 21.0.10 - Available

Automation.Engine 24.1.0 - Available

Additional Information

Defect : AE-35236

Public short description EN: System outage can happen during high job load due to a deadlock situation.

Public description EN: A problem has been fixed where system outage could happen during high job load due to a deadlock situation.