]
James Perkins resolved LOGMGR-246.
----------------------------------
Resolution: Done
That part was resolved in LOGMGR-256. The fix will be in WildFly 18. Sorry for the
inconvenience.
Wildfly 16 incorrect working log zip rotator
--------------------------------------------
Key: LOGMGR-246
URL:
https://issues.jboss.org/browse/LOGMGR-246
Project: JBoss Log Manager
Issue Type: Bug
Components: core
Environment: Windows,
Oracle JDK 8
Reporter: Igor Dmitriev
Assignee: James Perkins
Priority: Critical
Fix For: 1.5.10.Final, 2.0.12.Final, 2.2.0.Final, 3.0.0.Final, 2.1.11.Final
My logging profile configuration is:
1)
{code:xml}
<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>
{code}
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)
{code:xml}
<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>
{code}
All work as expected, except each time corp.log reach 300k, appear pair .zip files with
same content?