https://issues.apache.org/bugzilla/show_bug.cgi?id=43867
--- Comment #23 from Aaron Digulla <[EMAIL PROTECTED]> 2008-07-07 11:11:35 PST --- Guys, for the last time: This is neither a bug in log4j nor in Tomcat! It's *always* *always* *always* *always* a bug in the deployed webapp. Yeah, you didn't see it in 1.2.14 but that doesn't the bug wasn't there: You just didn't *see* it. The root cause of the bug is that code of your webapp is executed *after* undeploy. The usual cause of the problem is a) a shutdown hook or b) a thread which your app starts and which isn't terminated during undeploy. The usual culprits: Starting your own threads without terminating them on undeploy, using a timer framework like Quartz, ActiveMQ (which you can't stop cleanly after having started it), things like that. Activate the debug switched for Tomcat, use your IDE to connect and watch the threads. That should give you a very good idea where the bug comes from. So IMHO, this is bug should be closed as INVALID. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
