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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
