You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/11/01 02:53:48 UTC

DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped

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 hoju@visi.com  2002-11-01 01:53 -------
Just wanted to note that I updated the libraries at the ftp addresses that I 
mentioned in my previous comment.

You can follow the instructions like normal, but if you want to see it working, 
you only have to copy barracuda-core.jar to WEB-INF/lib.  all other jars can 
stay where they are.  With barracuda-core.jar in WEB-INF/lib, the "...CL 
stopped" error doesn't ever happen, even after multiple remove/install cycles.

Oh, and Ceki asked me before whether the testcase was meant to show problems 
with log4j.  Just to clarify, this is *not* a log4j issue as far as I can tell.

Jake

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>