Port Conflict Results in Failure to Initialize Administrative Server
 Technote (FAQ)
 
Problem
When starting the administrative server , the Location Service Daemon (LSD) port conflicts with the SSLport value, causing the administrative server to fail during initialization.
 
Cause
The lsdPort and the LSDSSLPort assignments were the same, resulting in a conflict during startup.
 
Solution
The following exceptions appear in the tracefile:
[03.01.31 14:47:38:455 CST] 7e891342 ORBRas com.ibm.CORBA.iiop.GIOPImpl createListener P=656098:O=0:CT The following exception was logged java.net.BindException: The socket name is already in use.
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:414)
at java.net.ServerSocket.<init>(ServerSocket.java:182)
[03.01.31 14:47:38:460 CST] 7e891342 Server < initializeOrb
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is: java.lang.ClassCastException
java.lang.ClassCastException

at com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:284)[03.01.31 14:47:38:553 CST] 7e891342 AdminServer   X WSVR0009E: Error occurred during startupjava.lang.RuntimeException: com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is: java.lang.ClassCastException


at com.ibm.ws.runtime.Server.initializeOrb(Server.java:1440)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:939)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime0

(ManagedServer.java:407)at com.ibm.ejs.sm.server.AdminServer.

initializeRuntime0(AdminServer.java:1104)at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:391)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)

[03.01.31 14:47:38:631 CST] 7e891342 AdminServer   F WSVR0067E: Failed to initialize WebSphere Administration server


Check the <$WAS_HOME>/bin/admin.config file for conflicting port assignments.

For example:

com.ibm.ejs.sm.adminServer.bootstrapPort=900
com.ibm.ejs.sm.adminServer.lsdPort=9000
com.ibm.CORBA.LSDSSLPort=9010
com.ibm.CORBA.ListenerPort=1200
com.ibm.CORBA.SSLPort=1210

If conflicts are present, change one of the assignments to use a different port that is not currently in use.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 4.0
Software edition:
Reference #: 1145613
IBM Group: Software Group
Modified date: Mar 31, 2006