Troubleshooting
Problem
WebSphere processes like Application Server, Nodeagent or dmgr may fail to start with following exceptions: [9/26/14 13:26:54:355 EDT] 0000000a CoordinatorCo E HMGR0002E: HA Manager services on this process were not started. This server is not a member of a core group. [9/26/14 13:27:11:842 EDT] 0000000a ProcessRuntim W WWLM1014E: Server server1 on node myNode01 in cell myCell is not included in the distribution of work for the applications running in server server1. This is because the HAManager service is not available on server server1. Refer to other messages to discover the problems associated with the HAManager service.
Symptom
WebSphere Application Server or nodeagent or dmgr fails to start with the following exception:
[9/26/14 13:27:29:185 EDT] 0000000a WsServerImpl E WSVR0009E: Error
occurred during startup META-INF/ws-server-components.xml
[9/26/14 13:27:29:210 EDT] 0000000a WsServerImpl E WSVR0009E: Error
occurred during startup com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError:
Lookup of CoreStack service failed
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:199)
.
Caused by: com.ibm.ws.exception.RuntimeError: Lookup of CoreStack service failed
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.join(HAManagerMessagingEngineImpl.java:1117)
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.startConditional(HAManagerMessagingEngineImpl.java:875)
<<< The actual caused by error and stack might vary, but key is to look for HMGR0002E and WWLM1014E on startup. There is also a possibility that HMGR0021E can be thrown, which could be due to a corrupt file. >>>
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21449799