Adrian
asked on
WebSphere 6.1
Hi ,
I am working on WebSphere6.1
When i started the server i am getting the belowCaused by: com.ibm.ws.exception.Runti meError: Unable to initialize the Name Service
at com.ibm.ws.naming.bootstra p.NameServ erImpl.sta rt(NameSer verImpl.ja va:476)
at com.ibm.ws.runtime.compone nt.Contain erImpl.sta rtComponen ts(Contain erImpl.jav a:977)
at com.ibm.ws.runtime.compone nt.Contain erImpl.sta rt(Contain erImpl.jav a:673)
at com.ibm.ws.runtime.compone nt.ServerI mpl.start( ServerImpl .java:526)
at com.ibm.ws.runtime.WsServe rImpl.boot ServerCont ainer(WsSe rverImpl.j ava:192)
... 24 more
Caused by: com.ibm.ws.naming.distcos. NameSpaceC onstructio nException : Unable to start bootstrap server using port 2814. 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.bootstra p.NameServ erImpl.sta rtBootstra pService(N ameServerI mpl.java:7 71)
at com.ibm.ws.naming.bootstra p.NameServ erImpl.sta rt(NameSer verImpl.ja va: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.transpo rt.WSTrans port.creat eListener( WSTranspor t.java:859 )
at com.ibm.ws.orbimpl.transpo rt.WSTrans port.creat eListener( WSTranspor t.java:629 )
at com.ibm.rmi.iiop.Transport Manager.cr eateListen er(Transpo rtManager. java:174)
at com.ibm.rmi.iiop.ORB.creat eListener( ORB.java:9 01)
at com.ibm.CORBA.iiop.ORB.cre ateListene r(ORB.java :3318)
at com.ibm.rmi.iiop.Bootstrap Server.<in it>(Bootst rapServer. java:113)
at com.ibm.rmi.iiop.ORB.creat eBootstrap Server(ORB .java:910)
at com.ibm.CORBA.iiop.ORB.cre ateBootstr apServer(O RB.java:33 70)
at com.ibm.ws.naming.bootstra p.NameServ erImpl.cre ateBootstr apServer(N ameServerI mpl.java:8 25)
at com.ibm.ws.naming.bootstra p.NameServ erImpl.sta rtBootstra pService(N ameServerI mpl.java:7 64)
exception
Can you plz help on this.
Thanks a lot.
I am working on WebSphere6.1
When i started the server i am getting the belowCaused by: com.ibm.ws.exception.Runti
at com.ibm.ws.naming.bootstra
at com.ibm.ws.runtime.compone
at com.ibm.ws.runtime.compone
at com.ibm.ws.runtime.compone
at com.ibm.ws.runtime.WsServe
... 24 more
Caused by: com.ibm.ws.naming.distcos.
at com.ibm.ws.naming.bootstra
at com.ibm.ws.naming.bootstra
... 28 more
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.orbimpl.transpo
at com.ibm.ws.orbimpl.transpo
at com.ibm.rmi.iiop.Transport
at com.ibm.rmi.iiop.ORB.creat
at com.ibm.CORBA.iiop.ORB.cre
at com.ibm.rmi.iiop.Bootstrap
at com.ibm.rmi.iiop.ORB.creat
at com.ibm.CORBA.iiop.ORB.cre
at com.ibm.ws.naming.bootstra
at com.ibm.ws.naming.bootstra
exception
Can you plz help on this.
Thanks a lot.
netstat -an | grep 2814
ASKER
Hi
How do u know other profiles using same port?
Thanks
How do u know other profiles using same port?
Thanks
Login to administrative console. Maybe at url like this.
http://ip:port/ibm/console
There will be server menu on the left side, after click it. Please search for Port section. It will summarize all the ports used by websphere.
Actually, it is easier to check it by netstat -na|grep 2814 before running your server.
Hope this help,
Sompol
http://ip:port/ibm/console
There will be server menu on the left side, after click it. Please search for Port section. It will summarize all the ports used by websphere.
Actually, it is easier to check it by netstat -na|grep 2814 before running your server.
Hope this help,
Sompol
ASKER
Hi
Do i need to change the BootStrap Port on each JVM?
THanks
Do i need to change the BootStrap Port on each JVM?
THanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok.
Thank you.
Thank you.
I think my suggestion help the author solved the problem.
The port number 2814 is already opened and your server want to use for boot strap at the same port number.
You can check whethere this port already in-use before starting websphere by using this command-line
c:\>netstat -na|findstr 2814
If it already open, the status may be ESTABLISHED, or LISTENING.
To solve this problem, you need to check other websphere profile or other application going to using this port and then try manage port number without conflict.
Hope this help,
Sompol