Jobs in RUNNING status remain stuck in backlog

book

Article ID: 84529

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

Jobs display in a RUNNING status in the backlog even though the related scripts have completed at the system level.

Cause

The RmiServer Process is no longer evaluating the Jobs and they remain hung in a RUNNING status.

Environment

Release: CA Automic Applications Manager (AM) version 8.X.X and version 9.XX.

Resolution

Perform the following either of the following steps, ranked from least intrusive to most intrusive, in order to get the RUNNING status Jobs, as well as other stuck status such as the KILLING status, out of the queue:

  1. Stopping/Restarting the Automic Application Engineer (Master):
    • Select the Automic Application Engineer (Master) Summary and stop then start it.
      • ***NOTE: This may cause the Master to re-evaluate the status of the Jobs and move them to the history***
  2. Stopping/Restating the RmiServer Process:
    • From the command line with “sosite” invoked issue the following commands:
      1. stopso rmi
      2. startso rmi
    • ***NOTE: This will require all User’s to restart their instance of the Automic Application Manager (AM) Client***
  3. Delete the Jobs from the backlog utilizing a SQL statement:
    • As this option can lead to potential adverse effects on the Automic Application Manager (AM) instance, please contact Automic Support and reference this Knowledge Base (KB) Article and number to obtain the necessary SQL statements.