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

Remko Popma commented on LOG4J2-661:
------------------------------------

I have tried but am unable to reproduce the issue. Both with and without 
$$\{date} pattern rollover works as expected and rolls over every hour.

Is it possible you have another configuration file that is being picked up 
instead of the attached one?
Can you try changing your configuration to 
[code}
<Configuration status="trace">
{code}
and post the output you see on the console here?

> AsyncLogger with RollingFileAppender Daily Per Hour Not Working
> ---------------------------------------------------------------
>
>                 Key: LOG4J2-661
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-661
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders, Configurators
>    Affects Versions: 2.0-rc1
>         Environment: CentOS release 6.5 (Final)
> Memory 16GB
> AMD Phenom(tm) II X6 1090T Processor
> JBoss 7.1.0-cr1
>            Reporter: Bobby
>              Labels: async, daily, features, hourly, rolling
>         Attachments: log4j2.xml
>
>
> Using attached configuration i expect:
> router.log --> currently written file
> router.log.2014-06-20-00
> router.log.2014-06-20-01
> ...
> router.log.2014-06-20-23
> router.log.2014-06-21-00
> ...
> But instead i got:
> router.log
> router.log.2014-06-20-1 --> One day worth of logs
> I want to achieve daily rolling file with per hour rolling, so far I haven't 
> been able to produce the log with proper format, and as I remember, the 
> interval parameter seems like to increment by day not hour, like stated in 
> documentation.
> I have tried [[email protected]] suggestions to use $${date:yyyy-MM-dd} in 
> filePattern as suggested in 
> http://stackoverflow.com/questions/24051421/log4j2-asynclogger-rolling-file-appender-not-rolling-daily-per-hour,
>  but still got same result.
> I didn't however, test this in sync logger, because i need the async one, as 
> for sync one i already have with old log4j.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to