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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
