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 2013/01/23 08:46:12 UTC

[jira] [Commented] (LOG4NET-369) preserveLogFileNameExtension is not considered when rolling over time after an application restart

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

Dominik Psenner commented on LOG4NET-369:
-----------------------------------------

Patch commited as revision: 1437281
                
> preserveLogFileNameExtension is not considered when rolling over time after an application restart
> --------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-369
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-369
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.9
>            Reporter: Dominik Psenner
>            Assignee: Dominik Psenner
>            Priority: Minor
>             Fix For: 1.2.12
>
>
> Consider this configuration, with V 1.2.11 or trunk:
> <file value="log.log" />
> <appendToFile value="true" />
> <rollingStyle value="Composite" />
> <datePattern value=".yyyyMMdd-HHmm" />
> <staticLogFileName value="true" />
> <preserveLogFileNameExtension value="true" />
> * Start an application (a verbose one, preferably) with it.
> * Kill it immediately.
>   Log directory now looks like this
>   ---
>   log.log
>   ---
> * Wait until we are in another minute
> * Start application again
> * Kill it immediately
>   Log directory now looks like this
>   ---
>   log.log
>   log.log.20130122-2042
>   ---
> Didn't we say we want to preserveLogFileNameExtension?
> Shouldn't the file name of the file rolled over be "log.20130122-2042.log"?
> If the application weren't killed and restarted in another period,
> everything were correct.
> This happens when rolling over an old log file from a previous run upon application start. The line of this patch fixes it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira