tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped
Date Fri, 13 Jun 2003 23:10:28 GMT
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





------- Additional Comments From eric_schwarzenbach@classwell.com  2003-06-13 23:10 -------
I'm seeing this error with Tomcat 4.1.24 (LE jdk14), but under what seems a
somewhat different circumstance from what I'm seeing described here.

I have a servlet that performs a rather lengthy action (from doPost())--it takes
several minutes to complete. If I update the class while the doPost() is still
in the midst of processing, I see my servlet's destroy method called, then see
its init method called as it is reloaded. However the doPost method appears to
continue to run, judging by the output. It completes its task normally and
successfully, except that this "WebappClassLoader: Lifecycle error : CL stopped"
error keeps occuring.

I thought that destroy() was not supposed to be called until the service()
method has exited, which definitely has not happened in my case.

The reason I ran into this is I was testing the ability to take this servlet out
of service without risking interrupting current tasks...

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


Mime
View raw message