Monday, 3 October 2016

Websphere application server fails to start with WSVR0009E and createServerSocket

Cause:

Websphere application server fails to start with the following message.

SystemOut.log contains the following errors:

[2/6/15 11:09:38:111 CET] 00000000 WsServerImpl E WSVR0009E: Error occurred during startup com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000
minor code: 56 completed: No at
com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:463) at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539) Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid:
0x49421000 minor code: 56 completed: No at
com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:866) at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java

Resolution:

Check if the port 9100 is in use. Run netstat - a and look for the port in use. If its in use , change the port number in the serverindex.xm file under dmgr-profile-root/config/cells/cellName/nodes/nodename

Take a backup of the file before you modify.

Save and sync the changes and start the server.



No comments:

Post a Comment