WA DE (dSeries) Application stays in APPLHOLD / APPLWAIT

Products

• CA Workload Automation DE
• DSERIES- SERVER
• CA Workload Automation DE - Scheduler (dSeries)

Issue/Introduction

User tries to release a HOLD on an Application, but it stays in APPLWAIT state

Environment

Release : 12.2

Component : CA WORKLOAD AUTOMATION DE (DSERIES)

Cause

In some rare cases, there can be memory and DB sync issues.  This will result in application showing up in APPLWAIT state.  If application has Wait for previous generation, then next application generation will not run.  The following error message may be seen in the tracelogs:

20201206 06:27:47.217 [essential] [ERROR] DM.Appl.MYAPPL.1004: [2020-12-06_06:27:47.217] Exception: An exception in the handler class occurred. The exception is null.
com.ca.wa.publiclibrary.library.afm.AFMRouterException: An exception in the handler class occurred. The exception is null.
at com.ca.wa.publiclibrary.library.afm.AFMToAFMProcessorRouter.routeAfm(AFMToAFMProcessorRouter.java:177)
at com.ca.wa.comp.distributedmanager.workloadobject.WADmAFMProcessingManager.processMessage(WADmAFMProcessingManager.java:756)
at com.ca.wa.comp.distributedmanager.workloadobject.WADmAFMProcessingManager.processAllMessages(WADmAFMProcessingManager.java:591)

Resolution

• Perform a changerole in a High Availability configuration. This will clear the cache and will sync with the DB.
• Remove 'Wait for previous generation' or rename the application if changerole is not possible.
• Fixed in later release of DE, post 12.2. Suggest to upgrade to a supported release as 12.2 is EOS (February 28, 2025).