-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
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?
- causes
-
ENTMQBR-6608 new artemis.log file is not created when older files are compressed using logging.properties
- Closed
- is incorporated by
-
JBEAP-17081 [7.2.z] Upgrade jboss-logmanager from 2.1.7.Final to 2.1.13.Final
- Resolved
-
WFCORE-4479 Upgrade jboss-logmanager from 2.1.10.Final to 2.1.11.Final
- Resolved
- is related to
-
LOGMGR-256 Failure to rotate logfile on Windows system because of already open file lock
- Resolved