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=18134>. 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=18134 Logging stops if context is reloaded in Tomcat 4.0 ------- Additional Comments From [EMAIL PROTECTED] 2003-03-19 17:16 ------- do you call LogManager.shutdown() upon context shutdown? This can be done in a servlet context listener (contextDestroyed()). If you don't do this, then the JVM may keep a handle on your file and not allow another process to write to it (the other process, of course, being Log4j in the restarted context). See if that fixes your issue. I'm not sure about the "reloadable" attribute issue. However, it is not recommended that you put an app in production with reloadable="true". That is really meant for ease of development. I wouldn't trust something that brings that kind of complexity for production. Jake --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
