Deadlocks during workflow execution - if tasks within the workflow have MAX_PARALLEL restrictions set

book

Article ID: 87756

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
ORA-00060: deadlock detected while waiting for resource

A problem has been solved where deadlocks occured during workflow execution if tasks within the workflow have MAX_PARALLEL restrictions set.

Further technical details:
When a workflow with several parallel task has been started , several EXEC_LOH messages were send.
The deadlock occurs in the QUITT2 message for GENX that was send by one of the earlier EXEC_LOH messages. While the QUITT2 message is processed, one of the other EXEC_LOH is also processed and that is resulting in a deadlock.

The following server routines can be found in the logs of the WP´s:
JPEXEC_R/EXEC_LOH
JPEXEC_R/JPENDE / JPEXEC_R/DEACT
JPEXEC_R/QUITT2


 

Cause

Cause type:
Defect
Root Cause: Refer to description

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Version(s):
Automation.Engine in version 11.2.2 - Available
Automation.Engine in version 11.1.4 - Available
Automation.Engine in version 10.0.8 - Available

Additional Information

Workaround :
N/A