|
Problem |
When the security is enabled, the following errors show up
in the tracefile:
Encountered an exception in the main method java.rmi.RemoteException: ;
nested exception is:
com.ibm.ejs.EJSException: Could not register with Location Service
Daemon; nested exception is:
java.lang.ClassCastException
com.ibm.ejs.EJSException: Could not register with Location Service Daemon;
nested exception is:
java.lang.ClassCastException
and more below.
WebSphere is running properly but when the security is enabled the
following errors show up in the tracefile.
[01.03.14 19:44:00:918 EST] b824ee AdminServer F Encountered an exception
in the main method java.rmi.RemoteException: ; nested exception is:
com.ibm.ejs.EJSException: Could not register with Location Service
Daemon; nested exception is:
java.lang.ClassCastException
com.ibm.ejs.EJSException: Could not register with Location Service Daemon;
nested exception is:
java.lang.ClassCastException
java.lang.ClassCastException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.lang.RuntimeException.<init>(RuntimeException.java:37)
at java.lang.ClassCastException.<init>(ClassCastException.java:36)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at
com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at
com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at
com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at
com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at
com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:830)
at
com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:566)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:986)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360) |
|
Cause |
One cause for this exception happens when the ORB assigns
a dynamic port number to the LSDSSLPort and that port number is being used
by another process.
Another possible cause for this exception occurs when you have installed
a new certificate in a multi-node environment but did not install the new
certificate to all nodes.
|
|
Solution |
!. One cause for this exception happens when the ORB
assigns a dynamic port number to the LSDSSLPort and that port number is
being used by another process.
Solution:
Add the following lines in the admin.config file to set an alternate
port,
then re-enable security and restart the admin server.
(Make sure that the port is not used by using netstat -a)
com.ibm.CORBA.SSLPort=unusedPort-1
com.ibm.CORBA.LSDSSLPort=unusedPort-2
Additionally you may want to also set
com.ibm.CORBA.BootstrapPort=unusedPort-3
Where unusedPort-n are between 1200 and 8000
2. Another cause for this exception occurs when you have installed a new
certificate in a multi-node environment but did not install the new
certificate to all nodes.
Solution:
Insure that after you have created a new certificate, it is available to
all nodes attached to the WebSphere domain, such as, WebSphere servers
sharing the same WebSphere Application Server repository. Also, make sure
all the WebSphere servers have been recycled. |
|
|
|
|
|
|