Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.2.9, 1.2.10
-
None
-
Windows 2003 Server
Description
The following logging configuration will produce an endless loop of warnings under the following circumstances:
<appender name="AppRollingFileAppender" type="log4net.Appender.RollingFileAppender">
<param name="Threshold" value="ALL"/>
<param name="File" value="Log\\Audit
audit.txt" />
<param name="AppendToFile" value="true" />
<param name="MaxSizeRollBackups" value="-1" />
<param name="RollingStyle" value="Date" />
<param name="StaticLogFileName" value="true" />
<param name="CountDirection" value="1" />
<param name="DatePattern" value=".yyyyMMdd" />
<layout type="log4net.Layout.PatternLayout">
<param name="ConversionPattern" value="%date [%c(%property
)-<%ndc>] - %message%newline" />
</layout>
</appender>
1.) set your system clock back at least three days
2.) run an application to create the static log file dated 3 days prior
3.) set your system clock forward a day (i.e. from Monday to Tuesday)
4.) run the application again, the log file will roll and a new static log file is written
5.) set your system clock forward a day (i.e. from Monday to Tuesday)
6.) run the application
repeated warnings will be issued until the application is killed
log4net:WARN RollingFileAppender: Cannot RollFile [E:\tmp\LoggingFileLockBug\LoggingFileLockBug\bin\Debug\Log\Audit\audit.txt.XXX] -> [E:\tmp\LoggingFileLockBug\LoggingFileLockBug\bin\Debug\Log\Audit\audit.txt.20060719.XXX]. Source does not exist
where XXX is infinitely incremented until the process is halted
Two workarounds found so far both involve changing the date pattern. Both "yyyyMMdd" and ".yyyy-MM-dd" seem to work without issue.
Attachments
Attachments
Issue Links
- is superceded by
-
LOG4NET-367 RollingFileAppender-NG: rewrite the RollingFileAppender
- Open