[ https://issues.apache.org/jira/browse/LOG4J2-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16710562#comment-16710562 ]
Ralph Goers commented on LOG4J2-2517: ------------------------------------- Interesting. Was something viewing the orchestrator.log file? These errors mean what they say - Windows won't let the file be renamed if it is being accessed by something. There is no way around that. But the file name still makes no sense unless orchestrator.log was created on Sept 25 2018 at 18:50:48. > 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)