Jobs in Running status remain stuck in backlog

Document ID : KB000084529
Last Modified Date : 29/08/2018
Show Technical Document Details
Jobs display in a Running status in the backlog even though the related scripts have completed at the system level.
RmiServer is no longer evaluating the Jobs and they remain hung in a RUNNING status.
The following actions can be taken to try and get these RUNNING Jobs out of the queue, and applies to other stuck statuses as well such as KILLING status. They are in order of having the least to the most impact on the AM instance. 
  1. Stop and restart the Automation Engine (Master).
Highlight the Automation Engine in the Agent summary and stop and start it. This will sometimes cause the Master to re-evaluate the status of the Jobs and move them to history.
  1. Stop and restart the RmiServer.
From the command line with sosite invoked issue:
stopso rmi
startso rmi
Note:  This will require all User's to restart the Application Manager (AM) Client.
  1. Delete the Jobs from the backlog using a SQL statement.
As this can cause adverse effects on the AM instance, contact Automic Support for the SQL statements.  Reference this KB and the details will be provided.