Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-914

Compression of log files is omitted when application is stopped at rollover

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.5.7
    • 1.0.11
    • None
    • None
    • Debian Linux 2.6.26, Tomcat 6.0.28, SLF4J 1.7.5, Logback 1.0.11

    Description

      I have an embedded device logging performance data in a 30 second interval with a hourly rollover and enabled compression (zip). In case the application is stopped at rollover and started later on the old file does not get compressed.

      This is slightly related to LOGBACK-162 which was about not deleting old files when the application was stopped at rollover.

      I would highly appreciate if it were made impossible to have any uncompressed files except the current one.

      As a solution I'd propose that when cleanHistoryOnStart is set to true, a scan through the history is performed (probably already implemented) and in case an uncompressed file is found the compression is triggered.

      Thanks a lot,
      Alex

      Attachments

        Activity

          People

            logback-dev Logback dev list
            lauperalex Alexander Lauper
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: