Applications Manager master is in a Trouble status

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

The most common cause of Trouble status is described in article "Automation Engine intermittently goes into TROUBLE status"

A less common cause to Trouble status or if the database is a single node database is have multiple "eligible" RmiServers. Additional RmiServers can become eligible when migrating the server of the RmiServer or by changing the server host/IP.

A list of RmiServers and Agents can be found in the Rmi Servers tab within the Connections window.

More information about the Connections can be found in the documentation under the below page topic:

Viewing Server and Agent Connection Information

 

Cause

Applications Manager may be communicating with multiple RmiServers

Resolution

Ensure that the only eligible RmiServer is the current valid RmiServer. 

To access the View Connection window, we need to select from the Java client > View > View Connections > Rmi Servers tab

You will see a window similar to the below:

What you should see is a number of Session IDs belonging to the Host column value "Master" and the "Agent" column value RmiServer. If there are no Session IDs, this tells us that Applications Manager is not "fully" connected to the database which is why we are seeing Trouble status.

What we want to look at is the LAST column where there are rows with the value OK.

Unless you have a secondary RmiServer, there should be ONLY 1 row with the value OK. This value will also have the Agent column value "RmiServer".

If you have multiple rows with the with an OK, we need to change this value to No for all old or invalid connections. For every OK value, look at the host, IP address, and Last activity column value. If the host and IP does not match the current RmiServer host and IP, or if the last activity shows a really old date, we want to double click on the value OK. You will get a prompt that says "Disallow this RmiServer from being the Automation Engine". Select the OK button and the value will change to No.

Continue to do this until there is one value of OK where the host and IP is the currently correct host/IP for the RmiServer. If there is a secondary RmiServer, this entry should also have an OK value.

After making changes, restart the RmiServer process.