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 "Dominik Psenner (JIRA)" <ji...@apache.org> on 2014/09/02 15:59:20 UTC

[jira] [Resolved] (LOG4NET-439) Log file overwritten by rollingLogFileAppender after date-change with rolling style = date

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

Dominik Psenner resolved LOG4NET-439.
-------------------------------------
    Resolution: Duplicate

Keeping a maximum number of backups when rolling over date/time boundaries is currently not supported.

> Log file overwritten by rollingLogFileAppender after date-change with rolling style = date
> ------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-439
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-439
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.13
>         Environment: Windows XP, Windows server 2008, .Net 4.0
>            Reporter: Gerard de Leeuw
>            Priority: Minor
>
> When logging from the main thread after a date change and the maxsize of backups is reached, the existing log lines of other threads is removed from the file (or file is overwritten). Logging from other (sub) threads don't affect the file contents.
> Relevant appender configuration:
> <lockingModel type="log4net.Appender.FileAppender+MinimalLock" />
> <appendToFile value="true" />
> <staticLogFileName value="false" />
> <rollingStyle value="Date" />
> <datePattern value="yyyy-MM-dd'.log'" />
> <maxSizeRollBackups value="2" />



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)