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 that is already bound to another application, such as another instance of an appserver.
- 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.
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," [HP-UX]
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.
Related tasks
Tuning operating systems
Set transport chains