WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

The server process does not start or starts with errors

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. Verify that no ports are listening. Use the command: .
  2. Verify that no ports are listening. Use this CL command:
    NETSTAT *CNN
    
  3. Restart the server

For current information available from IBM Support on known problems and their resolution, see the IBM Support page. You should also refer to this page before opening a PMR because it contains documents that can save you time gathering information needed to resolve a problem.

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, seeTroubleshooting help from IBM.




Related tasks
Troubleshooting by task
Troubleshooting by component

Related reference
Installation problems

Reference topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_appsrvstart.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)