[LOG4J2-550] .log files are left un-archived after JVM restart

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-rc1
• Component/s: Core
• Labels: Rollover
• Assignee: Unassigned
• Reporter: Bohdan Mushkevych
• Created: 24/Feb/14 20:23
• Updated: 08/Sep/14 20:35
• Resolved: 08/Sep/14 20:35

Description

I am using log4j 2.0-rc1, StructuredDataMessage and EventLogger to perform dynamic logging.

Attached log4j2.xml configuration meant to:

• rotate log files on hourly basis OR after file reaches 64 MB (whatever comes first)
• archive logs that does not satisfy the file pattern

Whenever JVM is restarted, log4j abandons "old" files un-archived:

rw-rr-. 1 root root 317625 Feb 24 20:16 2014022419-sim-mdmlocal.mobidia.com.log
rw-rr-. 1 root root 3333648 Feb 24 20:20 2014022420-activity-mdmlocal.mobidia.com.log

Listing above shows that file 2014022419-sim-mdmlocal.mobidia.com.log was last touched by the system at 20:16, and should have been archived to .log.gz after restart, which occurred soon after

Issue Links

• depends upon: LOG4J2-448 StringIndexOutOfBounds when using property substitution
• is related to: LOG4J2-551 TimeBasedTriggeringPolicy is not triggering file roll-over