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 18:23:48 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

markt@apache.org changed:

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



------- Additional Comments From markt@apache.org  2004-07-12 18:23 -------
I think you are wrong. Let me try to explain.

In your initial report you quote two stack straces. Both of these start at
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run

This is a shutdown hook that is registered with the JVM at tomcat startup. 
When JVM shuts down (System.exit(), CTRL-C on windows, catalina stop etc) this 
shutdown hook is executed. The exceptions you are seeing are as a result of 
this shutdown code.

My point is that something is causing the JVM to shutdown. As part of the 
shutdown process the JVM calls the shutdown hook. During the running of the 
shutdown hook some exceptions occur and this is what you are seeing.

The hard part here is trying to work out what is causing the JVM to exit in 
the first place. I have previously checked every call in the tomcat code to 
System.exit() and they are all preceeded by a log message. On this basis I 
think you can rule out any tomcat code. Is there a System.exit() in one of 
your webapps? Something that might be worth trying is running under a security 
manager that would thow a security exception if a webapp tried something like 
this. It is also possible that the OS is signalling the JVM to shutdown. 
Tracking this down could be trickier.

If you wish to discuss this further please use the tomcat-user mailing list as 
it is more appropriate to this type of discussion.

---------------------------------------------------------------------
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