|
Problem(Abstract) |
Installation of ContentManager in WebSphere® Application
Server v5.0.2.6 creates a new Application Server, then deploys the
ContentManager application. During startup of that newly-created
Application Server, the following exception is issued, and the server does
not start successfully. Security is disabled.
[9/2/04 15:43:30:267 EDT] 3b2ea3c0 WsServer E WSVR0003E: Server
icmrm failed to start com.ibm.ws.exception.RuntimeError
at
com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurit
yComponentImpl.java:164)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl
.java(Compiled Code))
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServ
erImpl.java:134)
---- Begin backtrace for nested exception
java.lang.RuntimeException
at
com.ibm.ws.management.component.JMXConnectors.stateChanged(JMXConnectors
.java:1224)
at
com.ibm.ws.security.core.SecurityComponentImpl.fireStartedEvent(Security
ComponentImpl.java:865)
at
com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityCom
ponentImpl.java:610)
at
com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurit
yComponentImpl.java:159)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl
.java(Compiled Code)) |
|
|
|
Cause |
The sslConfig value in server.xml file has a misspelled
hostname. |
|
|
Resolving the
problem |
Server.xml, located under Install_Root
/config/cells/cell_name/nodes/node_name/
servers/server_name/ has the following value for sslConfig:
<properties xmi:id="Property_1094144774704"
name="sslConfig"value="hrexjs02/DefaultSSLSettings"/>
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_1094144774709" sslEnabled="true"
sslConfig="hrexjs02/DefaultSSLSettings">
<transports xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_1094144774711" sslEnabled="true"
sslConfig="hrexjs02/DefaultSSLSettings">
After correcting the hostname from hrexjs02 to hrexejs02,
the server starts successfully.
If the problem appears in a federated cell environment, update the
server.xml file at the ND level configuratio, then perform a full
synchronization, which pushes the updated server.xml out to the node
level. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|