DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=27371 java.lang.ThreadDeath caused by log4j when reloading Tomcat app [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2004-03-03 05:17 ------- This is generally caused by using configureAndWatch() when configuring Log4j which starts up a thread which won't stop unless specifically shut down by LogManager.shutdown(). This should be done in the contextDestroyed() method of a servlet context listener. I have never seen this issue since I began calling shutdown(). BTW, if you are using configureAndWatch() in a web environment, don't. It isn't a good idea. Better to have a configuration servlet or other mechanism to dynamically modify Log4j workings at runtime than to have Log4j spawn a thread. It will only cause you grief. I'm marking this as worksforme. Please reopen if the suggested solution does not work for you. Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
