[
https://issues.apache.org/jira/browse/LOG4J2-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945472#comment-13945472
]
Ralph Goers commented on LOG4J2-550:
------------------------------------
That is because you have two date Lookups and no date conversion. You have to
have one %d to control the time the file rollover will occur. All other date
references should be lookups with the doulble '$' to cause the date to be
resolved every time the pattern is calculated.
> .log files are left un-archived after JVM restart
> -------------------------------------------------
>
> Key: LOG4J2-550
> URL: https://issues.apache.org/jira/browse/LOG4J2-550
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-rc1
> Reporter: Bohdan Mushkevych
> Attachments: log4j2.xml
>
>
> I am using log4j 2.0-rc1, StructuredDataMessage and EventLogger to perform
> dynamic logging.
> Attached log4j2.xml configuration meant to:
> - rotate log files on hourly basis OR after file reaches 64 MB (whatever
> comes first)
> - archive logs that does not satisfy the file pattern
> Whenever JVM is restarted, log4j abandons "old" files un-archived:
> -rw-r--r--. 1 root root 317625 Feb 24 20:16
> 2014022419-sim-mdmlocal.mobidia.com.log
> -rw-r--r--. 1 root root 3333648 Feb 24 20:20
> 2014022420-activity-mdmlocal.mobidia.com.log
> Listing above shows that file 2014022419-sim-mdmlocal.mobidia.com.log was
> last touched by the system at 20:16, and should have been archived to .log.gz
> after restart, which occurred soon after
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
