During ZDU Java based Agents crash with traces

book

Article ID: 84697

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
java.lang.NullPointerException
at com.uc4.ex.GenericConfiguration.rewriteCPList(GenericConfiguration.java:609)
at com.uc4.ex.AdminRoutine.logon(AdminRoutine.java:406)
at com.uc4.ex.ExecutorLifecycle.logon(ExecutorLifecycle.java:344)
at com.uc4.ex.ExecutorLifecycle.execute(ExecutorLifecycle.java:129)
at com.uc4.ex.sap.UCXJR3X.main(UCXJR3X.java:69)

While performing a Zero Downtime Upgrade (ZDU) the point where the Agent is reconnecting will occasionally cause Java based agents (i.e. SAP, SQL, etc.) to crash.

The following error message is displayed and trace files are thrown.

U02003012 An unknown message from partner '##SYSTEMNAME##CPNUMBER' could not be processed

Shortly after the Agent crashes with the error messages described under "Error Message".

This occurs on SAP and other Java based Agents (SQL, RA,...) occasionally, it does not always occur.

The error was found with Agents in Version 12.0, but it is possible that older agents will also show this behavior


 

Cause

Cause type:
Defect
Root Cause: During a ZDU if an Agent goes down it is not automatically started and can result in a null pointer exception error and trace files.

Environment

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

Resolution

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

Fix Status: Released

Fix Version(s):
Component(s): Java based Agents

Automation Engine 12.1.1 - Available

Additional Information

Workaround :
When performing a ZDU using Agent version 12.0, be sure to check to ensure all Agents are still up and running after the point where the Agents should reconnect.  If there are any Agents that are down, manually start them.