Transport chain problems

Review the following topics if we 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:

• We are trying to bind the channel to a port already bound to another application, such as another instance of an application server.

• We 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 -a command from a command prompt to display the state of the port to which we are trying to bind.

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

• (iSeries) We 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 we are trying to bind.

  To change the amount of elapse time that must occur before TCP/IP can release a closed connection and reuse its resources, see Tune operating systems.

(HPUX)

Error message CHFW0030E indicates there is "No such file or directory",

If we receive an Error message CHFW0030E that indicates there is no such file or directory, and we are running on an HP-UX operating system, make sure we have the most current patches for that operating system installed.

Tune operating systems