tomcat-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 Oct 2005 16:08:09 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





------- Additional Comments From remm@apache.org  2005-10-24 18:08 -------
(In reply to comment #36)
> 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.

I don't see the point of blaming log4j as is. It's the same problem with any
shared library which would keep objects related to a webapp, while at the same
time being disconnected from the lifecycle (at best, memory leaking will occur).
I'd say the concept is to be blamed, but there are few solutions.

Problems can also be caused by not setting the context classloader well (I did
fix some more issues related to this in 5.5.9+, as JULI is quite sensitive to
that). I think the current code is now clean related to this.

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message