Jobs remain in RUNNING status is Agent host is restarted

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

If an Agent's host machine is restarted while Jobs are in a Running status on said Agent, those Jobs will remain in a Running status

Environment

Applications Manager 9.x

Cause

Process ID of Running Jobs are lost during the host restart and Applications Manager does not recheck against missing Process ID

Resolution

A fix will be included in Applications Manager version 9.6.1 and/or 9.5.4

Fixed version(s) of Applications Manager will re-insert Jobs back into the "monitoring" list when Job's Agent is restarted. Monitoring list will check for Process ID and if not found will change the Job status to correct status of DIED.

Workaround:

Manually kill the Job from Java Client