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

Products

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

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

Release: 21.x & 24.x

Component: Unix Java Agent

Cause

DE178481

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 - Available

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.

Resolution Text: A problem was identified, whereby on UNIX systems in general, but AIX with the highest probability, non-terminal process events like STOP or CONTINUE or the checking call being interrupted could have resulted in handling the process as being terminated, although the process still has the potential to run further.