logback / LOGBACK-1553 [Open] Logs not getting zipped and growing in gbs taking diskspace ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1553 ============================== Issue created ------------------------------ Ayyasamy Radhakrishnan created this issue on 17/Mar/21 12:45 AM Summary: Logs not getting zipped and growing in gbs taking diskspace Issue Type: Bug Affects Versions: 1.2.3 Assignee: Logback dev list Attachments: disk270.log Components: logback-classic, logback-core Created: 17/Mar/21 12:45 AM Environment: Windows Server 2016.  We are using logback framework with the config on the info mode <configuration debug="true" scan="true" scanPeriod="30 seconds" ><configuration debug="true" scan="true" scanPeriod="30 seconds" > <shutdownHook class="ch.qos.logback.core.hook.DelayingShutdownHook"> <delay>10000</delay> </shutdownHook>     <appender name="fileinfo" class="ch.qos.logback.classic.sift.SiftingAppender"> <!-- This is MDC value --> <!-- We will assign a value to 'fis.logfilename' via Java code --> <discriminator> <key>fis.logfilename</key> <defaultValue>defaultlogger-${bluepumpkin.ProcessName}</defaultValue> </discriminator> <sift>   <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender">     <file>${IMPACT360DATADIR}/Logs/Integration Server/${fis.logfilename}-logback.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${IMPACT360DATADIR}/Logs/Integration Server/zip/${fis.logfilename}-logback.%d\{yyyy-MM-dd-HH}.%i.log.zip</fileNamePattern> <!--fileNamePattern>${IMPACT360DATADIR}/Logs/Integration Server/${fis.logfilename}-logback.%d\{yyyy-MM-dd}.%i.log.zip</fileNamePattern--> <!--Keep archive for hours specified below (7days * 24 Hours, as rolling policy is by hour as fileNamePattern includes HH)--> <maxHistory>168</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <!-- rollover when the file reaches the size below--> <maxFileSize>30MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <encoder> <pattern>####[${fis.processname}]-[${user.name}] [%date\{yyyy-MM-dd HH:mm:ss.SSSZ}] [%level] [%thread] [%logger\{-2}] <##[\{user=${user.name}}]##> - %message%n</pattern> </encoder>   </appender> </sift> </appender> <logger name="org.eclipse.jetty.server.HttpChannel" level="OFF"/> <logger name="org.eclipse.jetty.http.HttpGenerator" level="OFF"/> <logger name="org.eclipse.jetty.io.WriteFlusher" level="OFF"/> <logger name="org.eclipse.jetty.server.HttpOutput" level="OFF"/>    <!--Staffing Calc logger Filter-->    <logger name="com.bluepumpkin.bpxCommon.common.Base.StopWatch" level="OFF"/> <root level="INFO"> <appender-ref ref="fileinfo" /> <appender-ref ref="file" /> </root> </configuration> Labels: TimeBasedRollingPolicy Priority: Major Reporter: Ayyasamy Radhakrishnan Description: We have multiple jvms running.. they are supposed log the info. For some reason the log file is not getting zipped up and keep on growing for multiple days. Beyond the max size configured.  Small sample attached from the 250MB file logs attached.. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)