|
Problem(Abstract) |
Seeing following error codes when trying to start IBM®
WebSphere® Portal Server: WSVR0003E and WSVR0009E. |
|
Symptom |
The following error is encountered when trying to start
portal server:
[1/15/06 20:30:44:062 CST] 4c71339f WsServer E WSVR0003E: Server
WebSphere_Portal failed to start
com.ibm.ws.exception.RuntimeError
at
com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.java:138)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:140)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
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 java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
---- Begin backtrace for nested exception
java.lang.NullPointerException
at
com.ibm.ws.webcontainer.WebContainer.startTransports(WebContainer.java:637)
at
com.ibm.ws.runtime.component.WebContainerImpl.startTransports(WebContainerImpl.java:319)
at
com.ibm.ws.runtime.component.WebContainerImpl.vetoableChange(WebContainerImpl.java:343)
at
java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:239)
at
java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:259)
at
java.beans.VetoableChangeSupport.fireVetoableChange(VetoableChangeSupport.java:156)
at
com.ibm.ws.runtime.component.ComponentImpl.setState(ComponentImpl.java:95)
at
com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.java:132)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:140)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
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 java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[1/15/06 20:30:44:062 CST] 4c71339f WsServer E WSVR0009E: Error occurred
during startup |
|
Cause |
Portal server's server.xml file shows that the following
ports are defined:
<address xmi:id="EndPoint_2" host="*" port="9444"/>
<address xmi:id="EndPoint_3" host="*" port="9091"/>
<address xmi:id="EndPoint_4" host="*" port="9044"/>
<address xmi:id="EndPoint_1093473705394" host="*" port="9081"/>
The systemout.log file shows that:
Transport HTTP is listening on port 9,091.
The netstat -an was run before starting the server and it showed that port
9091 was not in use. So all the above settings for the port are correct.
So the cause is really not determined but the solution does exist. |
|
Resolving the
problem |
Reassign port 9091 in server.xml file to another port that
is not in use and then start the server. The server should startup. You
will then need to modify virtualhost.xml file to add an alias. This can be
done by going to console->environment->virtual hosts->select the
virtualhost being used. Click on new and add the new port with Host Name
as "*" |
|