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, 24 May 2004 14:07:23 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 tvo@informatik.uni-kiel.de  2004-05-24 14:07 -------
I think there is a solution for the above problem (stack trace).
Normally you call the logger within each class like this:

Logger myLogger = Logger.getLogger(MyClass.class)

Now lets suppose yout classes name is not MyClass but instead MyOwnClass and 
you call your logger
as shown above. Then the argument does not match the correct class name
and you will get the described stack trace.

So check each call of your logger for the appropriate class names. That should 
fix the problem.


Thorsten

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