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=3888>. 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=3888 WebappClassLoader: Lifecycle error : CL stopped [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Blocker Status|RESOLVED |REOPENED Priority|Other |High Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-10 17:28 ------- >You get the errors when some object which was loaded by the old > webapp classloader tries to run code. Ah...this is the first time you have specified when the error occurs. Now, if the classloader has been properly destroyed (generally you need to set it to be null), why is the old code even able to run? Since the old code is loaded in the now null classloader, then the JVM should not allow that code to run. Maybe there is classloader caching going on (ie: the reference to the old classloader is not being properly destoryed)? Also, I still say this is a bug in Tomcat's classloader system because I have been doing servlet development for years (this bug is now more than a year old) with several different servlet containers and have never seen this bug. In fact, it didn't start happening until I had started using that version of Tomcat 4. Also, I still see this bug still happens all the time for me...even with the 4.0.6 version of Tomcat. Remy, something is broken and it isn't user error. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
