Server fails to start with com.ibm.ws.exception.RuntimeError exception
 Technote (troubleshooting)
 
Problem(Abstract)
WebSphere® Application Server might fail to start if an invallide hostname occurs in the server.xml file, or if the HTTP Transport port is in use by some other process.
 
Symptom
You might see the following exception in Install_Root /logs/servername/SystemOut.log file.

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:123)
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
java.lang.NullPointerException
at com.ibm.ws.webcontainer.WebContainer.startTransports(WebContainer.java:611)
at com.ibm.ws.runtime.component.WebContainerImpl.startTransports(WebContainerImpl.java:319)

Review the attached Exception.log for a complete stack trace.

 
Resolving the problem
  1. Open the server.xml file in a text editor. This file is found:
    <Install_Root>/config/cell/cellname/nodes/nodename/servers/
    servername/server.xml


  2. Search for the transports XML tag.

  3. Note all of the HTTP Transport ports and the hostname in all transports XML tags.

  4. Run netstat -an to make sure that the HTTP transport port defined in server.xml file is not is use by any other process.

  5. Ensure that the defined hostname is a valid hostname in the server.xml file.

    1. If it is not a valid, change it to an asterisk (*), or change it to a valid hostname. Save the server.xml file.

    2. If the hostname is a valid hostname, edit the etc/hosts file to make sure it has a valid machine name. If not, change it to a valid machine name.

  6. Start the server.

On a newly created server, you might have this issue only after deploying an application, because the HTTP Transport port initializes only if there is an application deployed and started during the server startup.

You will see the following line in the SystemOut.log file only if there is an application deployed in that server:


[12/23/04 7:54:51:792 EST] 31ce1b81 HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[12/23/04 7:54:53:545 EST] 31ce1b81 HttpTransport A SRVE0171I: Transport https is listening on port 9,090.

 
Exception.log
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1.1.2
Software edition:
Reference #: 1195378
IBM Group: Software Group
Modified date: Sep 28, 2007