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 [EMAIL PROTECTED] 2005-10-24 17:32 ------- although many comments say log4j has nothing to do with it which is theoretically probably true, most of the time it appears like log4j is causing the issue. my latest threaddeath which i get around 5 times per day I suppose after about 5 reloads indicates INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.log4j.spi.ThrowableInformation. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. It does always appear to be this SPI class as long as I can remember. A naiive thought but perhaps if there were a way to stop this class entering loadClass at the wrong time the threaddeath would disappear for most common cases since everyone uses log4j with tomcat. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
