WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows

             Personalize the table of contents and search results

Server startup problems

If a server process does not start or starts with errors, the following topics might help you to diagnose the problem.

Installation program completes successfully, but an application server does not start, or starts with errors

Message "The socket bind failed for host hostname and port portnumber. The port may already be in use." occurs when restarting an application server.

The following error message might appear in the SystemOut.log after restarting an application server:
The socket bind failed for host hostname and port portnumber.  The port may already be in use.

This problem might occur if the network is slow, and the port listed in the message text did not finish listening when the application was stopped and restarted.

To verify that this is the problem, check the port status.

To correct this problem, wait for a few minutes after stopping the server:
  1. [AIX HP-UX Linux Solaris Windows] Verify that no ports are listening. Use the command:
    netstat -a 
  2. [i5/OS] Verify that no ports are listening. Use this CL command:
    NETSTAT *CNN
    
  3. Restart the server
IBM Support has documents and tools that can save you time gathering information needed to resolve problems as described in Troubleshooting help from IBM. Before opening a problem report, see the Support page:



Related tasks
Troubleshooting administration
Related reference
[AIX HP-UX Linux Solaris Windows] Installation problems
Reference topic    

Terms of Use | Feedback

Last updated: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rtrb_appsrvstart.html