Uploaded image for project: 'JBoss Log Manager'
  1. JBoss Log Manager
  2. LOGMGR-246

Wildfly 16 incorrect working log zip rotator

    XMLWordPrintable

Details

    Description

      My logging profile configuration is:

      1)

      <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="true"/>
</periodic-size-rotating-file-handler>

      File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size.

      2)

      <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true">
<level name="ALL"/>
<file relative-to="jboss.server.log.dir" path="corp.log"/>
<rotate-size value="300k"/>
<max-backup-index value="10000"/>
<suffix value=".yyyy-MM-dd.zip"/>
<append value="false"/>
</periodic-size-rotating-file-handler>

      All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content?

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-6608 new artemis.log file is not created when older files are compressed using logging.properties

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17081 [7.2.z] Upgrade jboss-logmanager from 2.1.7.Final to 2.1.13.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4479 Upgrade jboss-logmanager from 2.1.10.Final to 2.1.11.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. LOGMGR-256 Failure to rotate logfile on Windows system because of already open file lock

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              jperkins-rhn James Perkins
              idmitrieffv@gmail.com Igor Dmitriev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: