You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Bohdan Mushkevych (JIRA)" <ji...@apache.org> on 2014/02/24 21:32:19 UTC

[jira] [Created] (LOG4J2-551) TimeBasedTriggeringPolicy is not triggering file roll-over

Bohdan Mushkevych created LOG4J2-551:
----------------------------------------

             Summary: TimeBasedTriggeringPolicy is not triggering file roll-over
                 Key: LOG4J2-551
                 URL: https://issues.apache.org/jira/browse/LOG4J2-551
             Project: Log4j 2
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0-rc1
            Reporter: Bohdan Mushkevych


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-r--r--. 1 root root    96195 Feb 24 20:16 2014022419-guid_info-mdmlocal.mobidia.com.log
-rw-r--r--. 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-***




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org