DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27829>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27829 server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-07-12 12:40 ------- Sure, the exception came from the JVM, but why do you claim that the JVM is shutting down due to this? To me, it rather appears that the tomcat code neither bothers to i) catch and analyze java.net.SocketException which may well be of very temporary nature nor ii) provides a useful log-output that helps an admin to fix the issue without having to fully restart tomcat. it appears that unlockAccept() in PoolTcpEndpoint.java isn't prepared to do anything smart when a SocketException comes along - or am I wrong? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
