tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27829] - server diying after: SEVERE: Caught exception trying to unlock accept.\njava.net.SocketException: Network is unreachable
Date Mon, 12 Jul 2004 12:40:39 GMT
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

hauser@acm.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From hauser@acm.org  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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message