I have a logback configuration which specifies a daily rollover for a java swing application that is connected to a legacy backend and creates much log: <appender name="LocalFile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${logdir}/local.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <!-- daily rollover --> <fileNamePattern>${logdir}/local.%d{yyyy-MM-dd}.log</fileNamePattern> <!-- keep 10 days' worth of history --> <maxHistory>10</maxHistory> </rollingPolicy> <encoder> <pattern>%d [%t] %-5p %c{2} - %m%n</pattern> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> </appender> I am finding in production that sometimes the logfile doesn't roll. I am not sure whether the application is running at the moment when it's supposed to roll, if that matters. Initially I suspected Windows 7 permissions - a bloody nightmare - were responsible. I initially thought that it always rolled correctly on some machines, but not on others. But now I find a case on a single machine where rollovers happened on some days but not on others. We are using logback v.1,0.7 and slf4j version 1.6.5. Yes, I know there are more recent versions but it would be a major hassle getting them deployed into our particular environment and I haven't seen this behavior in months of testing. Can anyone point me in a direction leading to the solving of this issue?