logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Bodewig (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (LOG4NET-27) Rolling files on date/time boundaries doesn't support a maximum number of backup files.
Date Fri, 06 Apr 2012 05:32:09 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248077#comment-13248077
] 

Stefan Bodewig edited comment on LOG4NET-27 at 4/6/12 5:32 AM:
---------------------------------------------------------------

This issue may be the one with the most votes, but if you search around JIRA you'll see RollingFileAppender
is broken in so many ways.  I think it is responsible for about a third of all reports.

Last summer when we waded through the issues to triage what should go into 1.2.11 I deliberately
left out all RFA issues as - to be honest - I don't think it can be fixed without rewriting
it.  Back then some people started to work on a new implementation so this decision seemed
to be a good one.

Unfortunately life has interfered with the efforts of back then, as with the time I can devote
to log4net myself.  I'll look into the latest incarnation of this patch but honestly would
prefer a re-thought and re-written RFA myself.

Are there enough people watching this issue who would actually be able to build log4net from
svn trunk to verify it fixes their problem (and doesn't introduce new ones) before I'd cut
a new release?
                
      was (Author: bodewig):
    This issue may be the one with the most votes, but of you search around JIRA you'll see
RollingFileAppender is broken in so many ways.  I think it is responsible for about a third
of all reports.

Last summer when we waded through the issues to triage what should go into 1.2.11 I deliberately
left out all RFE issues as - to be honest - I don't think it can be fixed without rewriting
it.  Back then some people started to work on a new implementation so this decision seemed
to be a good one.

Unfortunately life has interfered with the efforts of back then, as with the time I can devote
to log4net myself.  I'll look into the latest incarnation of this patch but honestly would
prefer a re-thought and re-written RFA myself.

Are there enough people watching this issue who would actually be able to build log4net from
svn trunk to verify it fixes their problem (and doesn't introduce new ones) before I'd cut
a new release?
                  
> Rolling files on date/time boundaries doesn't support a maximum number of backup files.
> ---------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-27
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-27
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 1.2.11
>            Reporter: Florian Ramillien
>            Priority: Minor
>             Fix For: 1.2 Maintenance Release
>
>         Attachments: LOG4NET-27.patch, RollingFileAppender.cs, RollingFileAppender.cs,
RollingFileAppender.cs, RollingFileAppender.cs.patch, RollingFileAppender.patch
>
>
> A maximum of backup files exist when rolling files on file size, but not for rolling
on date/time.
> This can be implemented with the same config key : MaxSizeRollBackups

--
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

        

Mime
View raw message