ppkarwasz commented on issue #3068: URL: https://github.com/apache/logging-log4j2/issues/3068#issuecomment-2405009206
That commit is a fix to [LOG4J2-1906](https://issues.apache.org/jira/browse/LOG4J2-1906) and is probably related to #2297, where a regression occurred. Anyway I believe that those issues are independent of this one: - your problem affects only the **first** rollover after the JVM starts. At this time Log4j Core uses the timestamp on the current log file to deduce when the last rollover must have occurred. - those issues deal with the timestamp that is used in **all** rollovers. After the first rollover, Log4j Core does not need to check the filesystem to find out when the last rollover happened. :wink: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
