[jira] [Updated] (LOG4NET-82) RollingFileAppender: Cannot RollFile ... Source does not exist

2011-09-20 Thread Stefan Bodewig (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig updated LOG4NET-82:
--

Fix Version/s: (was: 1.2.11)
   1.2 Maintenance Release

 RollingFileAppender: Cannot RollFile ... Source does not  exist
 ---

 Key: LOG4NET-82
 URL: https://issues.apache.org/jira/browse/LOG4NET-82
 Project: Log4net
  Issue Type: Bug
  Components: Appenders
Affects Versions: 1.2.9, 1.2.10
 Environment: Windows 2003 Server
Reporter: Kenneth Oberleitner
Assignee: Roy Chastain
 Fix For: 1.2 Maintenance Release


 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=.MMdd /
   layout type=log4net.Layout.PatternLayout
   param name=ConversionPattern value=%date 
 [%c(%property{log4net:HostName})-lt;%ndcgt;] - %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 
 MMdd and .-MM-dd seem to work without issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (LOG4NET-82) RollingFileAppender: Cannot RollFile ... Source does not exist

2011-09-05 Thread Stefan Bodewig (JIRA) 

 [ 
https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Bodewig updated LOG4NET-82:
--

Fix Version/s: 1.2.11

 RollingFileAppender: Cannot RollFile ... Source does not  exist
 ---

 Key: LOG4NET-82
 URL: https://issues.apache.org/jira/browse/LOG4NET-82
 Project: Log4net
  Issue Type: Bug
  Components: Appenders
Affects Versions: 1.2.9, 1.2.10
 Environment: Windows 2003 Server
Reporter: Kenneth Oberleitner
 Fix For: 1.2.11


 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=.MMdd /
   layout type=log4net.Layout.PatternLayout
   param name=ConversionPattern value=%date 
 [%c(%property{log4net:HostName})-lt;%ndcgt;] - %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 
 MMdd and .-MM-dd seem to work without issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (LOG4NET-82) RollingFileAppender: Cannot RollFile ... Source does not exist

2006-07-24 Thread Thorbjorn Kvam (JIRA) 
 [ http://issues.apache.org/jira/browse/LOG4NET-82?page=all ]

Thorbjorn Kvam updated LOG4NET-82:
--

Affects Version/s: 1.2.10

We are running v1.10, which is also affected.  Also, the reported workaround 
with changing the datepatterns doesn't help in our case. Tried both the 
suggested datePattern changes without luck. 

 RollingFileAppender: Cannot RollFile ... Source does not  exist
 ---

 Key: LOG4NET-82
 URL: http://issues.apache.org/jira/browse/LOG4NET-82
 Project: Log4net
  Issue Type: Bug
  Components: Appenders
Affects Versions: 1.2.9, 1.2.10
 Environment: Windows 2003 Server
Reporter: Kenneth Oberleitner

 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=.MMdd /
   layout type=log4net.Layout.PatternLayout
   param name=ConversionPattern value=%date 
 [%c(%property{log4net:HostName})-lt;%ndcgt;] - %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 
 MMdd and .-MM-dd seem to work without issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira