[
https://issues.apache.org/jira/browse/LOG4J2-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710467#comment-16710467
]
Jon Hanson edited comment on LOG4J2-2517 at 12/5/18 6:38 PM:
-------------------------------------------------------------
Well, the behaviour is different at least... What I now see is:
# The existing file *does* get renamed.
# The filename doesn't respect my rolling file pattern
(logs/orchestrator-%d\{MM-dd-yy-HH-mm-ss}-%i.log.gz):
## The actual filename is orchestrator-09-25-18-18-40-48-1.log (not sure why).
## It isn't compressed. That may be a config error on my behalf - will check.
# But, *the rolled file is empty*. I.e. it seems to be clearing out the
existing file before it rolls it.
was (Author: jonhanson):
Well, the behaviour is different at least... What I see now is:
# The existing file does get renamed.
# The filename doesn;t respect my rolling file pattern
(logs/orchestrator-%d\{MM-dd-yy-HH-mm-ss}-%i.log.gz):
## The actual filename is orchestrator-09-25-18-18-40-48-1.log (not sure why).
## It isn't compressed. That may be a config error on my behalf - will check.
# But, the rolled file is empty. I.e. it seems to be clearing out the existing
file before it rolls it.
> RollingFileManager OnStartupTriggeringPolicy never rolls the file on startup
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-2517
> URL: https://issues.apache.org/jira/browse/LOG4J2-2517
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.11.1
> Reporter: Jon Hanson
> Priority: Minor
> Attachments: log4j2.json
>
>
> I'm trying to get log4j2 (V2.11.1) to roll the existing log file at startup
> before it starts logging into a new file. My config is atached to the jira.
> I'm using a RollingFileManager with a OnStartupTriggeringPolicy with
> minSize=0, which, according to the documentation should be sufficient.
> However what i'm finding is that at startup, the
> {{OnStartupTriggeringPolicy}} class {{initialize}} method compares the
> timestamp of the log file to the JVM startup, and if the log file time is
> after the start-up time then it won't roll the file. If I step through the
> code then I see that at the point that check is made the file time is always
> after the JVM start time, because log4j2 appears to have already opened the
> file for writing at that point.
> More info here:
> [https://stackoverflow.com/questions/53632091/log4j2-rollingfilemanager-onstartuptriggeringpolicy-never-rolls-the-file-on-star]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
