Random Jobs are set to Ended_OK on Unix Java Agent when they were not even launched

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Agent Unix Java may set to Ended_OK wrongly some jobs in cases of heavy load (system or many jobs running in parallel).

This is quite hard to replicate and to detect when it occurs other than checking the database table AH and checking for a runid the value of the column ah_timestamp2 and comparing it with the start_time and end_time.

This can cause severe issues in case jobs are used as predecessors and so on.

Environment

Unix Java Agent 21.x and 24.x

Cause

DE178481

• The Issue: Under heavy system load, the service occasionally misidentified a process as 'closed' due to temporary system interrupts or unrelated status changes.
• The Fix: Migrated from waitpid to the waitid api call to specifically target 'exit' events and implemented a retry logic for system interrupts.
• The Result: Process tracking is now robust and no longer susceptible to the timing issues caused by high load.

Resolution

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

Fix version:
Component(s): Agent Unix Java

Automation.Engine 24.4.4 - Planned release March 2026

Additional Information

Public Title: On UNIX/AIX systems non-terminal events can lead to handling a process having exited.

Public Description: On UNIX/AIX systems non-terminal events can lead to handling a process having exited.