Scheduled jobs stop running after restart

Document ID : KB000084566
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

Shortly after restarting the Applications Manager (AM) processes, Jobs stop processing and remain in a STAGED status. Even when they are eligible to run, they never launch.

Looking in the logs Jobs appear to go to a STAGED (26) status and remain in that status until AM is restarted again.  Once the AM processes are restarted again, the stuck STAGED jobs go into a QUEUED status, are processed and will move to a FINISHED status.

Example:

Message that can be seen in the RmiServer log:


18:13:01.60 rfp0: 7 65966611 Q STAGED 26 oldStatus -1 originalStartDate 2017-02-19 18:12:00.0 startDate 2017-02-19 18:12:00.0 startedDate null cond false queue WEBM agent LXPRAS06 notification false
Environment:
OS Version: N/A
Cause:
Cause type:
Other
Root Cause: Need to check for a null agent from group to avoid NullPointerException errors when trying to find an agent to run the job. Root cause still in progress to determine why an null agent is returned.
Resolution:
Initial research indicates that there is a NullPointerException that is keeping the jobs from moving from a STAGED to a RUNNING status. AM is looking for an agent in the APPWORX_AGENTS group to run a job and something in the group data appears to be corrupt so it gets the exception because it can't find an agent to run the job on.  

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

Beginning in AM verson 9.2, a check has been added to check for a null agent from a group to avoid the NullPointerException errors when trying to find an agent to run the job.  Additional debugging has also been added to help reveal why a null agent is being returned occassionally when trying to find an agent to run the job.
 

Fix Status: Released

Fix Version(s):
Applications Manager 9.2 - Available
Additional Information:
Workaround :
Restart the Applications Manager processes.