WP Processes Crash and Generate Dumps After SQL Server Deadlock (Error 1205)
search cancel

WP Processes Crash and Generate Dumps After SQL Server Deadlock (Error 1205)

book

Article ID: 454471

calendar_today

Updated On:

Products

Automic Automation

Issue/Introduction

Automation Engine Work Processes (WP) crash unexpectedly and generate core dump files. The WP logs show a database error immediately preceding the crash:

U00003592 UCUDB - Status: '' Native error: '1205' Msg: '[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID XXX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.'

Upon checking the crash dump or backtrace, the failure often occurs in server routines such as JPEXEC_R or during the processing of the srv-acl-rest structure.

Environment

  • Product: Automation Engine version 24.4.3 or lower

Cause

The issue is caused by a dual-layered defect:

  1. Deadlock Trigger (Defect DE179469): A specific database access logic mismatch occurs when two WPs simultaneously attempt to update the Execution Handle (EH) table while performing a SELECT FOR UPDATE on the Activity Header (AH) table. This triggers the SQL Server 1205 deadlock.
  2. Initialization Bug (Defect DE179545): A COBOL-to-C conversion defect exists where the INITIALIZE statement for the srv-acl-rest structure is missing. When the deadlock forces a rollback, the process attempts to access this uninitialized memory structure, resulting in a segmentation fault and process crash.

Resolution

Update the Automation Engine to the following version or a newer service pack:

  • Automation Engine 24.4.5 (Available)