ESP DE Server does not start due to java.lang.NullPointerException

Products

• CA Workload Automation DE - Business Agents (dSeries)
• CA Workload Automation DE
• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

The DE server may not come up after a restart or changerole due to a new application that was added or imported.  An error like this is observed in the tracelogs:

2020XXXX 00:00:12.345 [essential] [ERROR] DM: [2020-XX-XX6_00:00:12.345] Calling into 911
java.lang.NullPointerException
 at com.ca.wa.comp.distributedmanager.workloadobject.CpResolver.isAllWobsComplete(CpResolver.java:309)
 at com.ca.wa.comp.distributedmanager.workloadobject.CpResolver.determineLatestWobsTimeBased(CpResolver.java:247)
 at com.ca.wa.comp.distributedmanager.workloadobject.CpResolver.determineLatestWobs(CpResolver.java:206)
 at com.ca.wa.comp.distributedmanager.workloadobject.CpResolver.processWob(CpResolver.java:334)
 at com.ca.wa.comp.distributedmanager.workloadobject.CpResolver.determineCriticalPath(CpResolver.java:136)

 

 

Environment

Release : 12.x

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Database: Any

OS: Any

Cause

If a new application was added or imported with a Link job, then it may have incorrect XML tags for Link and Task jobs.  The Link job may have Failure code with email specified.  This is not a valid tag for DE (ESP dSeries) and will result in null exception.

Note: The DE service will shutdown (crash) only on restart as the server will try to reprocess the application again in the active tables.

Resolution

A cold start is required to clean up the active tables of incorrect Link jobs.  The application will then need to edited.  Delete the current link jobs and recreate them.  This will add the link jobs with correct XML tags.