Troubleshooting an application server that will not start using the Network Deployment Manager administrative console
 Technote (troubleshooting)
 
Problem(Abstract)
Detailed steps for troubleshooting an Application Server that does not start using the Network Deployment Manager administrative console. This assumes that the application server node has been federated with the deployment manager.
 
Resolving the problem

Things to do:


1. Make sure the node agent is started.


2. From a command prompt:

  • On Windows®:

    a. Make $WAS_HOME\AppServer\bin the current working directory:

    > cd WAS_HOME\AppServer\bin

    b. Execute the serverstatus bat file:

    > serverstatus -all

    c. Start the node agent:

    > startNode

    You cannot use the administrative console to start the node agent initially. However, it can be used to restart it after it has been started using startNode command.

  • On Unix®:

    a. Make $WAS_HOME/AppServer/bin the current working directory:

    # cd $WAS_HJOME/AppServer/bin

    b. Execute the serverstatus script file:

    # ./serverstatus.sh -all

    c. Start the node agent:

    # ./startNode.sh

    You cannot use the administrative console to start the node agent initially. However, it can be used to restart it after it has been started using startNode command.



3. Make sure the HTTP transports are unique for the application server.

a. Execute netstat -an. Use > filenameto direct the output to a file.

b. Either from the administrative console (Servers > Application Servers Server with Issue > Web Container > HTTP Transports) or from the server.xml file for the application server (located at $WAS_HOME/DeploymentManager/config/cells/Network Name/nodes/I/servers/I/server.xml file and search for HTTPTransport), find the http transport for the application server.

c. Make sure that all the HTTP transports used by the application server are not already in use by comparing them to the netstat output.


4. Check stdout and stderr files for the application server that will not start. These logs are located in $WAS_HOME/AppServer/logs/<server name> directory.

5. Run the collector tool and call 1-800-IBM-SERV for further support from IBM®.

 
 
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 > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1080510
IBM Group: Software Group
Modified date: Jul 29, 2004