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 27371] - java.lang.ThreadDeath caused by log4j when reloading Tomcat app
Date Wed, 09 Feb 2005 00:08:03 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=27371>.
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=27371





------- Additional Comments From brett_s_r@yahoo.com.au  2005-02-09 01:08 -------
I'm not sure why this issue remains open, given that #26372 has been closed.

Whenever there is a ThreadDeath thrown from WebappClassLoader.loadClass() during 
a webapp restart, it is due to Tomcat invalidating the webapp's ClassLoader 
while threads are still executing a (long-running) service() method (or even 
lifecycle method).  Tomcat waits 2 seconds, then invalidates the ClassLoader and 
restarts the app, resulting in a ThreadDeath thrown by the ClassLoader if new 
class load requests occur.  See my comment in #26372 .

Given that #26372 has been marked invalid (read as -1 for a configurable [or 
perhaps longer] wait-time for current requests to complete, prior to 
invalidating the ClassLoader and restarting the webapp), I think that this issue 
should now be closed.

This is a Tomcat issue for restartable webapps, not a log4j issue.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

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