1. Server Manager Installation Guide
  2. BUG 14369731 - FOR SMC ON WAS 8.5 MANAGEMENT AGENTS SHOWING STOPPED IN HOME PAGE AFTER LOGIN

BUG 14369731 - FOR SMC ON WAS 8.5 MANAGEMENT AGENTS SHOWING STOPPED IN HOME PAGE AFTER LOGIN

Issue/ Resolution:

This issue is specifically for a Server Manager Console installed on WAS 8.5 (typically not applicable to Server Manager Console on WAS 7.x). The issue is caused because the JMX ports being used by the Server Manager Console (14501/14502 by default) are not freed during the self-update process and as a result, when the Server Manager Console application is updated and starts up it is unable to bind to the same JMX ports. Thus, the Server Manager Console now binds to the next free set of ports available. Because the Server Manager Agents connected to the Server Manager Console are not aware of this, they still attempt to connect to the old Server Manager Console port (14501 by default). As a result they show a status of stopped as the Server Manager Console and Server Manager Agents are not able to communicate. This is being investigated as to whether this is an EnterpriseOne Server Manager bug or a IBM WebSphere issue.

The resolution is to restart the Server Manager Console J2EE server after the self-update using these steps:

  1. Stop the Server Manager Console WAS J2EE container using:

    Z:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\stopServer.bat <server_name>

  2. Start the Server Manager Console J2EE server from the command line using:

    Z:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startServer.bat <server_name>

After applying these steps the Server Manager Agents connected to the Server Manager Console should show the correct statuses.