We currently experience a Warning logged in our stderrout log each time our application log rolls over. I think this has started after an upgrade of logback a while back. I can't find much info about what the problem might be in the forum or by googling. Anyone have an idea what the issue might be?
00:02:18,709 |-WARN in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@3640c655 - Unexpected periodsElapsed value 0
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${basedir:-.}/../logs/foo-${artifact}.%d{yyyy-MM-dd}.%i.log.zip</fileNamePattern>
<timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<maxFileSize>100MB</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
<maxHistory>60</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%property{hostname}] [%thread] [%X{auth_kontoid} %X{logid}] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>