I got "Caused by: com.ibm.ws.naming.distcos.NameSpaceConstructionException: Unable to start bootstrap server using port 2810. 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:771)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:471)
... 28 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:859)
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:629)
at com.ibm.rmi.iiop.TransportManager.createListener(TransportManager.java:166)
at com.ibm.rmi.iiop.ORB.createListener(ORB.java:871)
at com.ibm.CORBA.iiop.ORB.createListener(ORB.java:3300)
at com.ibm.rmi.iiop.BootstrapServer.(BootstrapServer.java:113)
at com.ibm.rmi.iiop.ORB.createBootstrapServer(ORB.java:880)
at com.ibm.CORBA.iiop.ORB.createBootstrapServer(ORB.java:3352)
at com.ibm.ws.naming.bootstrap.NameServerImpl.createBootstrapServer(NameServerImpl.java:825)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:764)
... 29 more
My Findings
1. Most of the time, a restart of the machine would solve the problem.
2. This happens when the port is being used by some other process (you can verify that using Windows netstat command)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:771)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:471)
... 28 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:859)
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:629)
at com.ibm.rmi.iiop.TransportManager.createListener(TransportManager.java:166)
at com.ibm.rmi.iiop.ORB.createListener(ORB.java:871)
at com.ibm.CORBA.iiop.ORB.createListener(ORB.java:3300)
at com.ibm.rmi.iiop.BootstrapServer.
at com.ibm.rmi.iiop.ORB.createBootstrapServer(ORB.java:880)
at com.ibm.CORBA.iiop.ORB.createBootstrapServer(ORB.java:3352)
at com.ibm.ws.naming.bootstrap.NameServerImpl.createBootstrapServer(NameServerImpl.java:825)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:764)
... 29 more
1. Most of the time, a restart of the machine would solve the problem.
2. This happens when the port is being used by some other process (you can verify that using Windows netstat command)
4 comments:
same problem for me too can any body suggest a solotion to me
Actuallu one or twise restatring resolves this issue for me but that took a lot of time ...
hoping of a suitable answer
Thanks in advance...
This issue occurs when we are starting the jvm with different functional ID other than wasadmin ID
Thanks Kamesh. Will check out this next time.
Post a Comment