Locked up port

[scohan]

What should I do if a co-worker is locked up on a port on our Linux box? This is what netstat outputs:

tcp 26 0 sherman:8009 sherman:47660 CLOSE_WAIT
tcp 26 0 sherman:8009 sherman:47653 CLOSE_WAIT
tcp 26 0 sherman:8009 sherman:47652 CLOSE_WAIT


And then he gets this trying to access it from weblogic:

<Jun 5, 2003 9:19:13 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to create a server socket on Channel Default for: 192.168.217.41, port: 8009. java.net.BindException: Address already in use Perhaps the address 192.168.217.41 is incorrect or another process is using port 8009.>
<Jun 5, 2003 9:19:13 AM EDT> <Emergency> <Security> <090085> <Server failed to bind to any port such that it is not reachable from the console.>

Thanks.

 

[pupu]

You are mixing up two things. The listing shows that there were some connections to port 8009 and weren't correctly finished, BUT it doesn't mean that another one cannot be created. Understanding this requires some TCP/IP background, sorry.

The error message probably means that there is some application already listening on port 8009, and another one is trying to bind to this port - and fails. Try 'lsof -i tcp:8009' to get PID of the first process, kill it (kill -9, for example) and try to restart the application.