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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-12-31 04:56 ------- I ran into this issue, and having written a trivial test case, I can confirm that this zilla has nothing to do with logging (commons or log4j) or parent classloaders etc. No amount of fiddling with library classloading will fix it. The real cause is that Tomcat is invalidating (through a call to stop()) the WebappClassLoader belonging to a servlet instance whose service() method runs a little longer than usual in some conditions (>2 seconds is enough). This can happen under heavy (server, DB) load, with threads still running in service(), and may occur in any lifecycle event that runs StandardWrapper.unload() e.g. stop, undeploy, reload, shutdown. If the longish service() method needs to load a class after unload() loses its patience, WebappClassLoader throws a ThreadDeath. Might want to leave this one open until I get a chance to log a couple of more concise zillas. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
