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-22 03:05 ------- The testcase I just uploaded provides Mark's testcase and includes a simplified version of my Log4jInit servlet. Logging is done via both a console appender and a FileAppender. The file appender is set up with a dynamic variable which points to where to write the file. As long as you install the app with the path "/locktest", you will find the file "main.log" in WEB-INF/logs of this webapp. No need to configure anything. It is all set up and ready to run. All source code including the classes that Mark didn't provide source to are provided (I decompiled his classes. I'm sure he doesn't mind). All source resides in the root of the webapp as well as the .jsp files which are what you need to run to see logging output. There is also a "running.txt" file which describes the URL to use to install/remove the webapp. Modify those example URL's to point to the "log4j_locktest" directory, which is the root of the webapp, on your system. Make sure this is installed *outside* of Tomcat's "webapps" directory. Any other place on your file system is appropriate. Any questions, let me know. Jake -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
