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] 2002-10-10 09:51 ------- Hey Remy, You say it is a user error. The only reasonable user error I can find, is that the placing of our lib files might leave something to question. Let me explain: We have one big web application. A Content Management System we're developing. Whenever we build a project using this Content Management System, we use the latest stable release of the thing. Since new versions of libraries we have not created come out all the time, we have the libraries in our web application also. This so that when we build our project, we have those versions of certain libraries that are compatible with our project. This does mean, that when we use for example log4j on one server, we do not place it in $Tomcat/common/lib or $tomcat/lib but in every web-app's WEB-INF/lib directory. As said, I know this is not a usage that the Tomcat documentation promotes. I do however feel, that IF this is the reason Tomcat's classloaders are crashing, this should not be possible to happen. If this is NOT the user error you're talking about, then please explain what you do mean. I've read the servlet spec, and read the tomcat documentation. If I don't know, that means a whole hell of a lot of people don't know either. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
