Unable to start standalone workstation for APM Enterprise Manager (EM) MOM after upgrade.

Document ID : KB000008808
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

APM Enterprise Manager (EM) MOM and Collectors are upgraded. After the upgrade Enterprise Manager (EM) MOM and Collectors start fine.

Then can launch standalone workstation or webstart workstation and connect to APM Enterprise Manager (EM) Collector. The workstation UI comes up successfully.

When launching standalone workstation or webstart workstation and connecting to Enterprise Manager (EM) MOM, the workstation UI does not come up successfully.

In task manager we continue to see the Java and workstation executable running when launching the standalone workstation.  The standalone workstation does not create logs even after enabling DEBUG.

Log file (IntroscopeEnterpriseManager.log) on Enterprise Manager (EM) shows the following in INFO mode.

[INFO] [PO:main Mailman 4] [Manager.SessionBean] Workstation User "admin" connected successfully from host "Node=Workstation_566, Address=xx.xx.xx.58/xx.xx.xx.58:61153, Type=socket"
[INFO] [PO Route Down Executor] [Manager.SessionBean] Workstation User "admin" disconnected successfully from host "Node=Workstation_566, Address=xx.xx.xx.58/xx.xx.xx.58:61153, Type=socket"

 

Log file (IntroscopeEnterpriseManager.log) on Enterprise Manager (EM) shows the following in DEBUG mode.


[INFO] [PO:main Mailman 5] [Manager.SessionBean] Workstation User "admin" connected successfully from host "Node=Workstation_848, Address=xx.xx.xx.58/xx.xx.xx.58:61153, Type=socket"

[DEBUG] [Dispatcher 1] [Manager.EventHandler] Error reading incoming bytes in Server Hub Receive 865 event handler for Socket Transport connected with Socket[addr=xx.xx.xx.58/xx.xx.xx.58,port=65111,localport=5001] because java.io.IOException: An existing connection was forcibly closed by the remote host
java.io.IOException: An existing connection was forcibly closed by the remote host
 at com.wily.isengard.postofficehub.link.v1.server.ByteBufferInputStream.readFromChannel(ByteBufferInputStream.java:297)
 at com.wily.isengard.postofficehub.link.v1.server.ByteBufferInputStream.readFromChannel2(ByteBufferInputStream.java:230)
 at com.wily.isengard.postofficehub.link.v1.server.ByteBufferInputStream.readFromChannel(ByteBufferInputStream.java:188)
 at com.wily.isengard.postofficehub.link.v1.server.ByteBufferInputStream.fillFromChannel(ByteBufferInputStream.java:176)
 at com.wily.isengard.postofficehub.link.v1.server.EventHandler.handleReadEvent(EventHandler.java:146)
 at com.wily.isengard.postofficehub.link.highconcurrency.Dispatcher.processHandlers(Dispatcher.java:158)
 at com.wily.isengard.postofficehub.link.highconcurrency.Dispatcher.doTask(Dispatcher.java:297)
 at com.wily.isengard.util.thread.AThreadedExecutable.run(AThreadedExecutable.java:192)
 at java.lang.Thread.run(Thread.java:745)

 

 

Environment:
APM Enterprise Manager (EM) MOM and Collectors upgraded from APM release 10.1 to APM release 10.5.2. on Linux.
Cause:

  Root cause is that <EM-Home>/ws-plugins directory contents are not upgraded successfully on the Enterprise Manager (EM) MOM.

Resolution:

1. Stop Enterprise Manager (EM) MOM.
2. Make a backup of the <EM-Home>/ws-plugins directory on EM MOM. 
3. Copy the <EM-Home>/ws-plugins directory from (EM) Collector to (EM) MOM.
4. Start the Enterprise Manager (EM) MOM.


Note: Same solution is applicable for Enterprise Manager (EM) Collector and Enterprise Manager (EM) Standalone.