[
https://issues.apache.org/jira/browse/LOG4J2-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710554#comment-16710554
]
Jon Hanson commented on LOG4J2-2517:
------------------------------------
I've just noticed that an error is being written to stdout:
{{2018-12-05 19:41:45,661 main ERROR Unable to move file logs\orchestrator.log
to logs\orchestrator-09-25-18-18-40-48-2.log: java.nio.file.FileSystemException
logs\orchestrator.log -> logs\orchestrator-09-25-18-18-40-48-2.log: The process
cannot access the file because it is being used by another process.}}
{{2018-12-05 19:41:45,669 main ERROR Unable to delete file
logs\orchestrator.log: java.nio.file.FileSystemException logs\orchestrator.log:
The process cannot access the file because it is being used by another
process.}}
These are the resultant log files:
{{-rw-rw-rw- 1 user group 0 Dec 5 19:39
orchestrator-09-25-18-18-40-48-1.log}}
{{-rw-rw-rw- 1 user group 0 Dec 5 19:41
orchestrator-09-25-18-18-40-48-2.log}}
{{-rw-rw-rw- 1 user group 825 Dec 5 19:41 orchestrator.log}}
> 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)
