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 Mon, 16 Jun 2003 15:21:21 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-16 15:21 -------
I noticed the mention of a timeout in the serlvet docs. I take it this timeout 
isn't explicitly configurable (except by hacking) in Tomcat?

This behavior seems kind of unclean... If it's going to time out shouldn't the 
engine kill the thread(s) rather than letting it(them) continue to run and 
throw errors? (Incidentally I realized my post() didn't totally run to 
completion...in the middle of one of the last steps it throws a 
java.lang.NoClassDefFoundError: java/lang/reflect/InvocationTargetException
attempting to instantiate a object via pluggable factory-style method.)

I could write my own synchronization between destroy() and service() but it 
seems like the kind of functionality that the framework should provide.

---------------------------------------------------------------------
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