|
I am yet to try version 1.1.5 in Production but our current system uses Logback 1.1.3 under JBOSS EAP 6.1 and java 1.7 on Linux. Our average production log files are usually rolled at midnight and can get as large as 400mb or more. We have been getting issues with the .tmp files for quite some time now. I moved from a time based rolling appender to a size and time based rolling appender a few weeks ago in Production based on comments I saw here and on google. Unfortunately the move has not resolved the issue. Our main log file configuration is as follows:
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>/apps/server/paygat01/log/paymentgateway.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/apps/server/paygat01/log/archive/paymentgateway.%d {yyyy-MM-dd}
.%i.log.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>50MB</maxFileSize>
</timeBasedFileNamingAndTriggeringPolicy>
<maxHistory>180</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%-5level | %d {ISO8601}
| %thread | %c | %m%n</pattern>
</encoder>
</appender>
We still get .tmp files left lying around. I thought the issue revolved around the log file size but splitting it up hasn't removed the issue. I will be implementing version 1.1.5 shortly. Could you confirm is this a fix version or does it simply contain extra debug to help actually resolve the issue.
|