DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=17498>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=17498 ------- Additional Comments From [EMAIL PROTECTED] 2006-08-28 10:38 ------- Created an attachment (id=18756) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18756&action=view) An alternate appender for daily rolling log files. DailyRollingFileAppender has issues when running in a multi-threaded environment, as a servlet container in it's nature is. The decision to roll over the file is handled within the appender, which in many cases may exist in several instances, possibly due to placement in the classloader hierarchy. Many of the appender instances may be unaware that the name of the file under their open file descriptor has changed. We have also experiences loss of logging data in this context, as DRFA deletes the log file if it already exists when performing the roll over. Have you tried placing log4j in the boot classpath, ensuring that it sits on top of the classloader hierarcy? In a web container, the .war files should NOT bundle log4j by themselves. I've attached an alternate appender we use for daily rolling. It avoids the issue by simply creating a dated log file in the first place. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
