|
Problem(Abstract) |
When starting application server in a ND/Base federated
environment it fails with following exception into SystemOut.log file :
[3/14/06 11:49:54:140 EST] 492c19ab WsServer E WSVR0003E: Server
WebSphere_Portal failed to start
com.ibm.ws.exception.RuntimeError
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:287)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
---- Begin backtrace for nested exception
com.ibm.ejs.EJSException: Could not register with Location Service Daemon,
which could only reside in the NodeAgent. Make sure the NodeAgent for this
node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:Response timed out
org.omg.CORBA.ORBPackage.InvalidName: LocationService:Response timed out
at
com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:212)
Above exception gets thrown even after confirming nodeagent was up and
running . |
|
|
|
Cause |
The following 2 property values of ORB Service had been
changed for this problematic server :
requestTimeout="20"
locateRequestTimeout="2"
Default value for these 2 properties are "180" . |
|
|
Resolving the
problem |
Preform the following to update these parameter values:
- Log into deployment manager adminconsole
- Expand Servers-->Application Servers
- Select server --> click on ORB Service under Additional
Properties section
- Modify the values here
- Save and synchronize changes with nodes
- Now you should be able to start the server
successfully
Note: If this problem appears in a stand alone server environment pls
contact IBM support for further help as it requires manual editing of
WebSphere appserver configuration file "server.xml" . |
|
|