com.ibm.ws.exception.RuntimeError: Unable to initialize the Name Service

com. ibm. ws. exception. RuntimeError: Unable to initialize the Name Service

* * * * * 1 votes

Published July 14th, 2008 in WebSphere

One more exception stacktrace from me. This time my WebSphere Commerce Test server produced this error. The error is very simple and I just thought of documenting it as there might be some people who still use WCS 5.6.1. The error I got was

[7/15/08 11:30:13:405 IST] 3cfdd9d3 WsServer      E WSVR0003E: Server server1 failed to start
com.ibm.ws.exception.RuntimeError: Unable to initialize the Name Service
	at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:462)
	........
Caused by: com.ibm.ws.naming.distcos.NameSpaceConstructionException: Unable to start bootstrap server using port 2809. Verify that no servers or other processes are already using the bootstrap server port. Also verify that the bootstrap server is being started with a user ID which has sufficient (e.g., root, Administrator) privileges.
	at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:736)
	at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:457)
	... 12 more
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:714)
	at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:619)

Unlike other WebSphere exception messages, just by reading the message we can find out why this error occurs. In the exception it clearly tells that ‘ Unable to start bootstrap server using port 2809. Verify that no servers or other processes are already using the bootstrap server port’. Yes that was the problem; I already had a WebSphere server running in my machine (An instance of WebSphere Process Server Test environment.) which is listening to the same port WCS is listening. I was trying to integrate WCS and WPS. When I stopped the WPS server, my WCS test client got started without any issues.

I think the problem is not specific to WCS or WPS any WebSphere based server may face the same problem when there is some port conflict.

Bookmark to