|
Problem(Abstract) |
After applying WebSphere® Application Server V5.0 Fix Pack
2, application servers created using wsinstance fail to start with the
following exceptions:
[8/5/03 17:26:12:549 PDT] 60e8fe21 WsServer E WSVR0003E: Server
server1 failed to start
com.ibm.ws.exception.RuntimeError
at
com.ibm.ws.runtime.component.ComponentImpl.setStartState(ComponentImpl.j
ava:138)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServ
erImpl.java:123)
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) |
|
|
|
Cause |
This error is due to an unresolved variable in the V5.0.2
$WAS_HOME/config/cell/<cell_name>/security.xml file.
<repertoire xmi:id="SSLConfig_1"
alias="$(node.name)/DefaultSSLSettings">
The node.name variable is left unresolved and does not match the one set
in
"cell/<cell_name>/nodes/<node_name>/servers/<server_name>/server.xml":
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_2" sslEnabled="true"
sslConfig="mother_test/DefaultSSLSettings"> |
|
|
Resolving the
problem |
The manual work around for this problem is to edit the
$WAS_HOME/config/cell/<cell_name>/security.xml file, and substitute
the actual node name for the node.name variable. |
|
|