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 an 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 -a
command from a command prompt 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.
- 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.
Error message CHFW0030E indicates there is No such file or directory
If you receive an Error message CHFW0030E that indicates there is no such file or directory, and you are running on an HP-UX operating system, make sure you have the most current patches for that operating system installed.