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 Mon, 24 Oct 2005 16:45: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=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 cowwoc@bbs.darktech.org  2005-10-24 18:45 -------
Remy,

I am using Tomcat 5.5.9, and log4j is only being loaded within the webapp
context (not global) and I still get this problem.

To date everyone keeps on talking theory but no one had yet to offer a practical
solution. Both Brett and Yoav have suggested one, which is to allow a
configurable timeout value before the ClassLoader is invalidated. Granted it's
not foolproof (who knows how big the timeout needs to be), but at least it's a
practical solution. You mention there are some other solutions, what are some of
your practical solutions to this problem?

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message