logging-log4j-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, 02 Aug 2004 18:45:49 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

java.lang.ThreadDeath caused by log4j when reloading Tomcat app





------- Additional Comments From ccorsi@exln.com  2004-08-02 18:45 -------
It looks like Ceki is right. I looked at the WebClassLoader source at it is
throwing the ThreadDeath exception because the WebClassLoader was stopped. Did
you not mention that you get this exception everytime that you hot deploy your
web application?

Here is the code within tomcat that is throwing the exception:

  // Don't load classes if class loader is stopped
  if (!started) {
     log.info(sm.getString("webappClassLoader.stopped"));
     throw new ThreadDeath();
  }

The sm variable is a static protected variable. It seems to me that it is not
properly being reset somehow.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message