[LOG4J2-551] TimeBasedTriggeringPolicy is not triggering file roll-over

• 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:30
• Updated: 08/Sep/14 20:36
• Resolved: 08/Sep/14 20:36

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

However, logging is performed on an "old" log minutes after new hour triggers:

rw-rr-. 1 root root 96195 Feb 24 20:16 2014022419-guid_info-mdmlocal.mobidia.com.log
rw-rr-. 1 root root 827184 Feb 24 20:16 2014022419-checkin-mdmlocal.mobidia.com.log

Listing above shows, that last logging was performed to file 2014022419-*** 16 minutes after filename was supposed to be changed to 2014022420-***

Issue Links

• depends upon: LOG4J2-448 StringIndexOutOfBounds when using property substitution
• relates to: LOG4J2-550 .log files are left un-archived after JVM restart