unsubscribe

On Thu, Jul 13, 2017 at 12:13 PM, Russ (JIRA) <[email protected]> wrote:

>
>      [ https://issues.apache.org/jira/browse/LOG4J2-1978?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Russ updated LOG4J2-1978:
> -------------------------
>     Attachment: log4j2.xml
>
> > Dated rolling files are incorrectly labeled with the date/time segment
> of the future iteration
> > ------------------------------------------------------------
> ----------------------------------
> >
> >                 Key: LOG4J2-1978
> >                 URL: https://issues.apache.org/jira/browse/LOG4J2-1978
> >             Project: Log4j 2
> >          Issue Type: Bug
> >          Components: Appenders
> >    Affects Versions: 2.8.2
> >            Reporter: Russ
> >         Attachments: log4j2.xml
> >
> >
> > Rolled dated log files have the wrong date, in relation to the enclosed
> dated log entries.
> > Rolled dated log file should mirror the date of the enclosed log entries.
> > Using the following example of a "daily rolling file" ...
> > * FilePattern: App_%d{yyyy-MM-dd}.log
> > * log entries for the date: (ie.) 2017-12-01 (note: the day is the 1st)
> > * are logged in base file named: (ie.) App_2017-12-01.log (note: the day
> is the 1st)
> > * The first occurrence of the roll should be midnight on the 2nd but
> that does NOT occur
> > * Log file App_2017-12-01.log now contains log entries for both
> 2017-12-01 and 2017-12-02
> > * The second occurrence of the roll is on the 3rd, and does occur,
> however...
> > * Log file App_2017-12-02.log is now having log entries for 2017-12-03
> written to it
> > This occurs similarly at any level of granularity, of the date/time
> iteration. For instance..
> > * with a FilePattern (focusing on the date pattern specifically) of:
> %d{yyyy-MM-dd_HH-mm}
> > * log entries for: 2017-12-01_08-32
> > * will be in the rolled file: 2017-12-01_08-31
> > Example log4j2.xml property file is attached.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Reply via email to