logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bohdan Mushkevych (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOG4J2-551) TimeBasedTriggeringPolicy is not triggering file roll-over
Date Wed, 09 Jul 2014 00:40:04 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055202#comment-14055202
] 

Bohdan Mushkevych edited comment on LOG4J2-551 at 7/9/14 12:39 AM:
-------------------------------------------------------------------

Ralph

I have tested today, and the original issue seams to be partially resolved.
i.e. it does not crash on double {color:red}$${color} anymore.

However, it seams that the {color:red}$${date:yyyyMMdd}{color} does not support {color:red}
\{GMT+XXX\} {color} suffix.
For instance, *filePattern*:
{code} filePattern="${log.path}/$${date:yyyyMMdd}{GMT+0}/%d{yyyyMMddHH}{GMT+0}-${sd:type}-${hostName}.%i.log.gz"{code}

produces folders with such names as: *20140708\{GMT+0\}*.  
How could I instruct {code}$${date:yyyyMMdd}{code} in filePattern to use UTC time zone?



was (Author: mushkevych):
Ralph

I have tested today, and the original issue seams to be resolved.
However, it seams that the {color:red}$${date:yyyyMMdd}{color} does not support {color:red}
\{GMT+XXX\} {color} suffix.
For instance, *filePattern*:
{code} filePattern="${log.path}/$${date:yyyyMMdd}{GMT+0}/%d{yyyyMMddHH}{GMT+0}-${sd:type}-${hostName}.%i.log.gz"{code}

produces folders with such names as: *20140708\{GMT+0\}*.  
How could I instruct {code}$${date:yyyyMMdd}{code} in filePattern to use UTC time zone?


> 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
>              Labels: Rollover
>         Attachments: log4j2.xml
>
>
> 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.2#6252)

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


Mime
View raw message