[logback-dev] [JIRA] (LOGBACK-1482) RollingFileAppender creates .tmp file while creating GZ file at midnight

QOS.CH (JIRA) noreply-jira at qos.ch
Thu Aug 29 09:56:00 CEST 2019

Abhijit Kangale created LOGBACK-1482:

             Summary: RollingFileAppender creates .tmp file while creating GZ file at midnight
                 Key: LOGBACK-1482
                 URL: https://jira.qos.ch/browse/LOGBACK-1482
             Project: logback
          Issue Type: Bug
          Components: logback-classic
    Affects Versions: 1.3.0-alpha4
         Environment: This is happening in production environment.
            Reporter: Abhijit Kangale
            Assignee: Logback dev list
            Priority: Critical
         Attachments: logback.xml

After migrating our servers to openjdk11 we started observing this issue.

We are using below configuration currently. We started using the latest versions of logback and slf4j.

















We are using 

SizeAndTimeBasedRollingPolicy as rolling policy and rollover is set at midnight. 


Basically the roll over happens properly creating .gz file but at the same time it creates .tmp file for application log.

-rw-r----- 1 iphsubmt iphsubmt  7805929 Aug 11 00:00 submissions-pipeline-metrics-2019-08-10.1.log.gz
-rw-r----- 1 iphsubmt iphsubmt     8216 Aug 11 00:34 submissions-pipeline-dead-letters.log
-rw-r----- 1 iphsubmt iphsubmt 14956341 Aug 11 14:33 submissions-pipeline-metrics-2019-08-11.0.log.gz
-rw-r----- 1 iphsubmt iphsubmt   416634 Aug 12 00:00 submissions-pipeline-2019-08-11.0.log.gz
*-rw-r----- 1 iphsubmt iphsubmt    13780 Aug 12 00:00 submissions-pipeline-2019-08-11.0.log2815836846996630.tmp*
I have referred all open and closed tickets on this topic but nothing helped to resolve our issue. So please. I have attached logbook.xml file we are using.

This message was sent by Atlassian JIRA

More information about the logback-dev mailing list