Error while starting the server

[Lee Sha]

Hi,

I get the below error message while starting the server. I doubt, it may be because of insufficient security privileges on my system. Can anyone help me in identifying the issue? Thanks for your time.

*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.1 [BASE 5.1.0.3 cf30412.02] [JDK 1.4.1 b0344.02] running with process name localhost\localhost\server1 and process id 3728
Host Operating System is Windows XP, version 5.1
Java version = J2RE 1.4.1 IBM Windows 32 build cn1411-20031011 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51
user.install.root = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51
Java Home = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51\java\jre
ws.ext.dirs = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/java/lib;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/classes;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/classes;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib/ext;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/web/help;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;D:/Program Files/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.2/runtime/worf.jar
Classpath = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/properties;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/properties;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib/bootstrap.jar;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib/j2ee.jar;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib/lmproxy.jar;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/lib/urlprotocols.jar;D:/Program Files/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wteServers.jar;D:/Program Files/IBM/WebSphere Studio/Application Developer/v5.1.2/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1.1/runtime/wasToolsCommon.jar
Java Library path = D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/bin;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/java/bin;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\runtimes\base_v51/java/jre/bin;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;.;D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\eclipse\jre\bin;D:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.5.0\bin;C:\Program Files\Oracle\jre\1.5.0\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Sybase\DLL;C:\Sybase\BIN;C:\Program Files\Sybase\Sybase Central\win32;C:\Sybase\ASEP;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program Files\Java\jdk1.5.0\bin;C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Documents and Settings\vinayag\.vmwebclient\Java\bin
************* End Display Current Environment *************
[2/29/08 21:09:56:548 IST] 3f90960e ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
[2/29/08 21:09:57:251 IST] 3f90960e AdminInitiali A ADMN0015I: AdminService initialized
[2/29/08 21:09:58:282 IST] 3f90960e Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[2/29/08 21:09:58:313 IST] 3f90960e SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[2/29/08 21:09:58:641 IST] 3f90960e SecurityCompo I SECJ0309I: Java 2 Security is disabled.
[2/29/08 21:09:58:657 IST] 3f90960e SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[2/29/08 21:09:58:657 IST] 3f90960e SecurityCompo I SECJ0240I: Security service initialization completed successfully
[2/29/08 21:09:58:673 IST] 3f90960e JMSRegistrati A MSGS0602I: WebSphere Embedded Messaging Client only has been installed
[2/29/08 21:10:00:313 IST] 3f90960e NameServerImp E NMSV0011E: 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.
org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
[2/29/08 21:10:00:532 IST] 3f90960e 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:402)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:105)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
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:640)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:397)
... 11 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:667)
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:616)
at com.ibm.rmi.iiop.TransportManager.createListener(TransportManager.java:157)
at com.ibm.rmi.iiop.ORB.createListener(ORB.java:804)
at com.ibm.CORBA.iiop.ORB.createListener(ORB.java:3299)
at com.ibm.rmi.iiop.BootstrapServer.<init>(BootstrapServer.java:109)
at com.ibm.rmi.iiop.ORB.createBootstrapServer(ORB.java:813)
at com.ibm.CORBA.iiop.ORB.createBootstrapServer(ORB.java:3351)
at com.ibm.ws.naming.bootstrap.NameServerImpl.createBootstrapServer(NameServerImpl.java:688)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:633)
... 12 more
---- Begin backtrace for nested exception
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:640)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:397)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:105)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
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:667)
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:616)
at com.ibm.rmi.iiop.TransportManager.createListener(TransportManager.java:157)
at com.ibm.rmi.iiop.ORB.createListener(ORB.java:804)
at com.ibm.CORBA.iiop.ORB.createListener(ORB.java:3299)
at com.ibm.rmi.iiop.BootstrapServer.<init>(BootstrapServer.java:109)
at com.ibm.rmi.iiop.ORB.createBootstrapServer(ORB.java:813)
at com.ibm.CORBA.iiop.ORB.createBootstrapServer(ORB.java:3351)
at com.ibm.ws.naming.bootstrap.NameServerImpl.createBootstrapServer(NameServerImpl.java:688)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:633)
... 12 more
---- Begin backtrace for nested exception
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:667)
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:616)
at com.ibm.rmi.iiop.TransportManager.createListener(TransportManager.java:157)
at com.ibm.rmi.iiop.ORB.createListener(ORB.java:804)
at com.ibm.CORBA.iiop.ORB.createListener(ORB.java:3299)
at com.ibm.rmi.iiop.BootstrapServer.<init>(BootstrapServer.java:109)
at com.ibm.rmi.iiop.ORB.createBootstrapServer(ORB.java:813)
at com.ibm.CORBA.iiop.ORB.createBootstrapServer(ORB.java:3351)
at com.ibm.ws.naming.bootstrap.NameServerImpl.createBootstrapServer(NameServerImpl.java:688)
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:633)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:397)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:105)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)

[2/29/08 21:10:00:563 IST] 3f90960e WsServer E WSVR0009E: Error occurred during startup

[Bryce Martin]

Is this a server that had been working and just starting failing on startup? Or is it a new install and the first server you have created and it has never worked?

[Lee Sha]

It was working before. Now it has stopped working.

[Lee Sha]

Hi, I stopped the server and restarted the system. It started to work again. I guess the last session was not closed properly. Some websphere utility was still holding the port 2809 which got released when I restarted the system. Thanks for all your time.

[Karim Soomar]

Hello,

I am getting a similar error for version 6.1.
The server has never been used, and I am trying to set it up for the first time.
Restart did not work.

Please help.

Thank you,

[Tiya Khambadkone]

I am facing exactly the same problem.
org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 exception.
Restarting the system did not work.
First time server starting...

[Jeff Hill]

As the log shows there are port conflicts. This could happen if your server wasn't terminated properly during your last session (which can happen if RAD crashes). Make a copy of stopserver.bat in your profile's bin directory and edit it to add the "server1" argument, then save it as stopserver1.bat. Run this any time and it will either stop whatever server instance is using that admin port, or report that the server "doesn't appear to be running".

Port conflicts can also happen if you are using a shared installation, such as when you use a Citrix ICA client. Citrix apparently doesn't virtualize ports, so two users can launch servers using the same profile (or at least profiles having the same port assignments) and the second instance will get the error. Note that if this guy then runs stopserver1.bat, it will kill the other person's running server <evil grin>

In short, in a shared environment it is esential to develop a strategy to ensure each developer has a profile with unique port assignments.

[Ramakanta Sahoo]

usual solution is to restart the machine or kill eacha nd every java process running on the machine for that id and then try again.

[Jeff Hill]

That's true, in a single-user environment. I'll bet, though, that at least some of the "me too" users above are working in a Citrix environment and don't realize that port conflicts can be an issue. As more enterprises move to shared environments (for reasons of cost, security, etc.), this is likely to become a common problem. This article from the IBM developer's network covers all the bases (except one - see below):

http://www.ibm.com/developerworks/rational/library/09/rationalapplicationdeveloperoncitrixpresentationserver/index.html

There is one additional port conflict to note: the debug daemon's listener port (8001). This port is not part of the port assignments governed by the profile, rather it is provided at launch by RAD. The symptom users will see is that they start a server in debug mode, but when they enter the debug perspective the "listen" button will be red, and when clicked will report the port conflict because another user's server is already using 8001.

So in addition to each user having a profile with unique port assignments, each must also select a unique debug daemon port (set this in Window > Preferences, Run/Debug > Debug Daemon). You can specify any available port number, but there are plenty of ports listed as unassigned in the 8000 range so choosing one there shouldn't be a problem. Team members will have to keep track of who's using which port, and remember to change the setting in every new workspace (i.e., make it part of your saved preferences).

[Marcel Friedmann]

Hi. thats a common error then a port conflict occurs.
If its a internal websphere port which is causing the trouble you can adjust the serverindex.xml of the AppServer instance directly. This is usually the easiest way :-) but it is dirty.

This post explains how to fix this error