You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Daniel (JIRA)" <ji...@apache.org> on 2012/05/03 03:03:48 UTC
[jira] [Commented] (LOG4NET-118) RollingFileAppender:
RollingStyle=Size with StaticLogFileName=false does not work
[ https://issues.apache.org/jira/browse/LOG4NET-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267072#comment-13267072 ]
Daniel commented on LOG4NET-118:
--------------------------------
This is definitely not a Minor issue! I just lost 1GB of logs because of it.
As Brian mentioned, this overwrites the existing log file instead of rolling and creating a new one.
Does anyone know if this is somehow fixed in 1.2.11 ?
> RollingFileAppender: RollingStyle=Size with StaticLogFileName=false does not work
> ---------------------------------------------------------------------------------
>
> Key: LOG4NET-118
> URL: https://issues.apache.org/jira/browse/LOG4NET-118
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.10
> Environment: Windows 2003 / Microsoft .NET Framework 2.0
> Reporter: Patrick Gautschi
> Priority: Minor
> Fix For: 1.2 Maintenance Release
>
>
> When using the an appender configuration like
> <appender name="InfoFile" type="log4net.Appender.RollingFileAppender">
> <file value="info.log" />
> <appendToFile value="false" />
> <encoding value="utf-8" />
> <countDirection value="1" />
> <maximumFileSize value="1MB" />
> <maxSizeRollBackups value="3" />
> <staticLogFileName value="false" />
> <rollingStyle value="Size" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%utcdate{yyyy-MM-dd HH:mm:ss.ff}Z [%thread] %-5level %logger - %message%newline" />
> </layout>
> </appender>
> results in the following error message when the application is started the second time:
> log4net:ERROR RollingFileAppender: INTERNAL ERROR. Append is False but OutputFile [V:\...\bin\Debug\info.log.0] already exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira