Merlijn van der Mee created LOGBACK-1350: -------------------------------------------- Summary: After rolling logback writes to the old and the new file. Key: LOGBACK-1350 URL: https://jira.qos.ch/browse/LOGBACK-1350 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Environment: Linux 2.6.32-696.el6.x86_64 Grails 3 application on tomcat 8.0.32 Reporter: Merlijn van der Mee Assignee: Logback dev list After rolling (without zipping) logback continues to log some threads to the old logfile and some to the new logfile. With statusListener(OnConsoleStatusListener) in logback.groovy I can see that the roll-over occurs twice. \{code} 17:00:02,500 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Elapsed period: Thu Nov 09 16:57:30 CET 2017 17:00:02,501 |-INFO in c.q.l.co.rolling.helper.RenameUtil - Renaming file [logs/jdbc-iom.log] to [logs/jdbc-iom.log.2017-11-09-16] 17:00:02,507 |-INFO in c.q.l.core.rolling.helper.TimeBasedArchiveRemover - first clean up after appender initialization 17:00:04,099 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Elapsed period: Thu Nov 09 16:56:22 CET 2017 17:00:04,100 |-INFO in c.q.l.co.rolling.helper.RenameUtil - Renaming file [logs/jdbc-iom.log] to [logs/jdbc-iom.log.2017-11-09-16] 17:00:04,104 |-INFO in c.q.l.core.rolling.helper.TimeBasedArchiveRemover - first clean up after appender initialization \{code} When rolling and zipping (what we actually use)  the second rolling gives an error since the zip file already exists and leaves the .tmp file. After this, it logs some theads to the new file and other threads to the xxx.tmp file.     -- This message was sent by Atlassian JIRA (v7.3.1#73012)