Hello,

 

Similar problem was already reported about a year ago:

 

http://mailman.qos.ch/pipermail/logback-user/2011-November/002706.html

 

I wonder if the problem is going to be fixed in the upcoming version.

If not, what should be the most simple workaround?

 

The most disturbing scenario related to this bug is that each value of a sifting attribute creates just one log file.

The sift appender configuration is set for compression.

The bug causes the log file to be left uncompressed, therefore no files are eventually compressed at all.

 

       <appender name="EXECUTION-SIFT" class="ch.qos.logback.classic.sift.SiftingAppender">

              <discriminator>

                    <key>userid</key>

                     <defaultValue>noname</defaultValue>

              </discriminator>

              <sift>

                     <appender name="EXECUTION" class="ch.qos.logback.core.rolling.RollingFileAppender">

                           <file>>${userid}.execution.log</file>

                           <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

                                  <!-- daily rollover -->

                                   <fileNamePattern>${userid}.execution.%i.log.zip</fileNamePattern>

                                  <maxIndex>100</maxIndex>

                           </rollingPolicy>

                           <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">

                                  <maxFileSize>${logFile.maxSize}</maxFileSize>

                           </triggeringPolicy>

                           <encoder>

                                  <pattern>%date{yyMMdd HH:mm:ss} %-5level %msg%n</pattern>

                                  <charset>UTF-8</charset>

                           </encoder>

                     </appender>

              </sift>

       </appender>

 

Thanks,

   Shaul



The information contained in this message is proprietary to the sender, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you.