Inconsistent time stamps in active objects cause WPs to core dump.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

If the client variable UC_CLIENT_SETTINGS has the following entry: DEACTIVATION_DELAY_TIME set to n minutes, some objects in the Process Monitoring perspective will get an End time < Start time, i.e.

The FAULT_ALREADY_RUNNING objects will get an AH_Timestamp4 < AH_Timestamp1 after the deactivation delay time is reached. In addition to that they also get a new RunID assigned.

SELECT AH_NAME,AH_IDNR, AH_CLIENT, AH_TIMESTAMP1, AH_TIMESTAMP2, AH_TIMESTAMP4, ah_status FROM AH WHERE  (AH_TIMESTAMP4 < AH_TIMESTAMP1 OR AH_TIMESTAMP4 < AH_TIMESTAMP2) and AH_STATUS >= 1800;

Environment

Release : 21.0.4

Cause

Defect.

Resolution

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

Article title: How to register to Broadcom Software Product updates and Critical Alerts

https://knowledge.broadcom.com/external/article?articleId=133819

Component: Automation Engine

Automation Engine 21.0.5 - Available

 

Public short description EN:
Finished JSCH executions are shown in Process Monitoring with Start Time greater than End Time.

Public description EN:
A problem has been fixed where already finished JSCH executions were shown in Process Monitoring with Start Time greater than End Time.