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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-05 10:44 --- can confirm that removal of log4j.properties from web application allows Tomcat to reload webapp gracefully after class compilation with dynamic class reloading on. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-05 11:43 --- Two questions: 1) Could you include the contents of your log4j.properties file. 2) Are you 100% sure that the trio - LogManager.shutdown(); - java.beans.Introspector.flushCaches(); - LogFactory.releaseAll();java.beans.Introspector.flushCaches() really gets called? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-04 09:50 --- i use log4j only by placing log4j.properties into classes in my web application, not programmatically as I think you are suggesting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-04 10:02 --- i use log4j only by placing log4j.properties into classes in my web application, not programmatically as I think you are suggesting. The log4j.properties file is parsed by PropertiesConfigurator. So you are indirectly invoking PropertiesConfigurator. Do you observe any difference if you remove log4j.properties file, i.e. not configure log4j at all? What do you observe if you call BasicConfigurator.configure() method? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 09:22 --- Can confirm that the ThreadDeath is still occurring after every class compile that causes a webapp reload by Tomcat resulting in total failure of Tomcat with the following in our contextDestroyed LogManager.shutdown(); java.beans.Introspector.flushCaches(); LogFactory.releaseAll(); - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-10-01 10:23 --- Allistair, Do you observe any difference when you configure log4j only by using BasisConfigurator.configure()? I mean without calling PropertyConfigurator or DOMConfigruator... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-09-30 15:05 --- Unless I hear that the combination of solutions offered in this thread does not address this problem, I will close this issue as WORKFORME soon. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-09-30 15:12 --- A couple of questions: 1) Does it actually work for you? 2) Does it work for Allistair Crossley ? 3) Wouldn't closing the report hide or obfuscate the information contained herein? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-09-30 15:17 --- I'm on it. Will let you know ASAP what the outcome of Introspector.flushCaches () is on this bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-09-22 14:12 --- Per Jay Paulsen's findings archived at http://marc.theaimsgroup.com/? t=10957839304r=1w=2, please try adding the Introspector.flush call and re- running the test. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-08-05 13:07 --- Relates to : http://issues.apache.org/bugzilla/show_bug.cgi?id=27371 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WONTFIX |
--- Additional Comments From [EMAIL PROTECTED] 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2004-05-11 14:15 --- The suggested fix of putting the log4j jars in WEB-INF/lib doesn't seem to work. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=26372 java.lang.ThreadDeath when trwaing to reload an application --- Additional Comments From [EMAIL PROTECTED] 2004-03-03 05:19 --- The problem has long been fixed by adding LogManager.shutdown() the contextDestroyed() method of a servlet context listener. I have mentioned this before, but for some reason no one takes notice. I'm writing it here so that at least there is a reference. Jake - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=26372 java.lang.ThreadDeath when trwaing to reload an application [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2004-01-23 11:54 --- This is the old issue of log4j trying to use the previous classloader (reloading will create a new classloader to load class definitions; see bug 3888). Maybe it would be good to leave this bug open so that people can complain using it, rather than file duplicates. However, I'd like everyone to know that the bug will never be fixed. You can probably fix the problem by putting log4 JARs (and the necessary commons-logging wrapper classes) inside the webapp repository. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
