Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 5 Aug 2004 11:52:37 -0000
Message-ID: <20040805115237.28662.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 26372]  -
    java.lang.ThreadDeath when trwaing to reload an application

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=26372>.
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=26372

java.lang.ThreadDeath when trwaing to reload an application

allistair.crossley@qas.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |


------- Additional Comments From allistair.crossley@qas.com  2004-08-05 11:52 -------
We are getting this a lot after recompilation of a class in a web app which 
makes Tomcat reload the application. 

However, we DO have the LogManager.shutdown in our servlet context listener but 
it does not solve the problem. 

	public void contextDestroyed(ServletContextEvent scE) {		
		LogManager.shutdown();  
	}

Interestingly this has only occurred the past 2 weeks since using 5.0.25. Prior 
to this we developed for 7 months with no problem on 5.0.19. So we just tried 
rolling back to 5.0.19 but it ALSO started happening there too. We find this 
behaviour very very odd. Furthermore we never had a LogManager.shutdown for 
those 7 months either. There is a lot of conflicting behaviour going on here 
and I would really like to know how to solve this as right now we are looking 
at having to rip out log4j which is bad news. 

SEVERE: Exception invoking periodic operation: 
java.lang.ThreadDeath
	at org.apache.catalina.loader.WebappClassLoader.loadClass
(WebappClassLoader.java:1229)
	at org.apache.catalina.loader.WebappClassLoader.loadClass
(WebappClassLoader.java:1189)
	at java.lang.ClassLoader.loadClassInternal(Unknown Source)
	at org.apache.log4j.spi.LoggingEvent.<init>(LoggingEvent.java:241)
	at org.apache.log4j.Category.forcedLog(Category.java:431)
	at org.apache.log4j.Category.log(Category.java:966)
	at org.apache.commons.logging.impl.Log4JLogger.error
(Log4JLogger.java:195)
	at org.apache.catalina.session.StandardManager.start
(StandardManager.java:659)
	at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4272)
	at org.apache.catalina.core.StandardContext.reload
(StandardContext.java:3021)
	at org.apache.catalina.core.StandardContext.backgroundProcess
(StandardContext.java:4629)
	at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChild
ren(ContainerBase.java:1619)
	at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChild
ren(ContainerBase.java:1628)
	at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChild
ren(ContainerBase.java:1628)
	at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run
(ContainerBase.java:1608)
	at java.lang.Thread.run(Unknown Source)

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