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 "Bharath Radhakrishnan (JIRA)" <ji...@apache.org> on 2011/03/17 08:08:29 UTC

[jira] Updated: (LOG4NET-289) RollPoint Topofminute in Rolling file appender sometimes rolls over more than once in a minute

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

Bharath Radhakrishnan updated LOG4NET-289:
------------------------------------------

    Description: 
When logging using the Rolling file appender, we are facing an issue of the roll over being occurring within a minute rather than on transition to the next minute. The roll over does occur correctly on transition to the next minute but sometimes it does occur without transition.
 
Is this  a reported issue or if it is fixed could you advise me how to get around this ?


  was:
When logging using the Rolling file appender, we are facing an issue of the roll over being occurring within a minute rather than on transition to the next minute. The roll over does occur correctly on transition to the next minute but sometimes it does occur without transition.
 


> RollPoint Topofminute in Rolling file appender sometimes rolls over more than once in a minute
> ----------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-289
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-289
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.10
>            Reporter: Bharath Radhakrishnan
>            Priority: Minor
>
> When logging using the Rolling file appender, we are facing an issue of the roll over being occurring within a minute rather than on transition to the next minute. The roll over does occur correctly on transition to the next minute but sometimes it does occur without transition.
>  
> Is this  a reported issue or if it is fixed could you advise me how to get around this ?

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