Why Port 6689 cannot be released - TechRepublic
General discussion
April 18, 2002 at 05:58 AM
akhan

Why Port 6689 cannot be released

by akhan . Updated 24 years ago

We have a web and Java based portal application called Viador running on Solaris 2.6. Viador is an application server that besides many other things consists of some JAVA processes. Viador server (software) can be stopped and re-started by application support group if there is problem (e.g., if application is responding slow etc.) It needs port # 6689 to run. It uses JRUN (the Java application server) and Netscape Web server to function. We often re-cycle Viador software to improve performance. But something strange happened recently. A few days ago the Unix box on which Viador is running had crashed and had to be restored from the back-up tape. After the server was restored, we can no longer stop and start Viador application server.When we attempt to restart Viador we get the error message “Port 6689 is unavailable”.

Since Viador needs port 6689 to function, it cannot be started until port #6689 is free and available. Our Unix SA has NOT been able to find the cause of port not being released. Also it cannot be determined which process is using and or keeping this port hostage and why the port cannot be released. Currently the only solution is to bring down and re-start Unix operation system. We do not like this solution since we have to depend on SA to do this. Also we should NOT have to re-boot Unix just to release a port from some rouge runaway process which cannot be identified.

Question: Is there any way to find out which process is using the port # 6689 and is there any command to release that port without re-booting Unix operating system. I believe there must be a command to identify which process is keeping this port hostage and free it up.

Any help would be highly appreciated. Thanks

This discussion is locked

All Comments