Transport chain problems

Review the following topics if you encounter a transport chain problem.

TCP transport channel fails to bind to a specific host/port combination

If a TCP transport channel fails to bind to a specific port, one of the following situations might have occurred:
  • You are trying to bind the channel to a port that is already bound to another application, such as another instance of a WebSphere Application Server.
  • You are trying to bind to a port that is in a transitional state waiting for closure. This socket must transition to closed before you restart the server. The port might be in TIME_WAIT, FIN_WAIT_2, or CLOSE_WAIT state. Issue the NETSTAT *CNN command from a command prompt line to display the state of the port to which you are trying to bind.

    If you need to change the amount of elapse time that must occur before TCP/IP can release a closed connection and reuse its resources, see Tuning operating systems.




Related tasks
Configuring transport chains
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 10:47:11 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-iseries&topic=rtrb_chain_trbl
File name: rtrb_chain_trbl.html