----------------------------- Please read the FAQ! <http://java.apache.org/faq/> ----------------------------- Hello, I am using version 1.0 on a Solaris 2.7 system with the Sun JDK 1.1.6. I have started JServ manually, and can use my servlets no problem. However, when I go to restart or shutdown JServ with the -r or -s switches, the last comment I get in the log is "Closing the server socket". Then the process doesn't die. After looking through the code, it looks like it is hanging up when it tries to close the socket. When it gets in this state, I have to kill the process so I can restart JServ. Does anyone know what would cause this behavior? Also wouldn't it be more robust to have it timeout after a while so it can continue to properly shutdown the servlets? Or else destroy the servlets first and then close the socket? As far as I can tell, using kill on the Java process doesn't hurt the socket so much as it may hurt all the servlets which don't get shut down properly. -Greg -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
