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

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

Thank you for attaching the trace log image file. I noticed that the trace log 
shows that WEB-INF/lib contains both log4j-core-2.0-rc1.jar and 
log4j-web-2.0-beta7.jar. The log4j-web module was removed in rc1. I recommend 
that you delete the log4j-web-2.0-beta7.jar file. (In rc2, log4j-web is a 
separate module again.)

I improved the status logging to show more detail on what is happening during a 
rollover. This is included in rc1, so if you can capture the status log during 
a rollover it would help with the investigation.

Also, about the log4j deadlock issue, log4j2 was specifically designed with 
more fine-grained locking to prevent issues like this. We have not had any 
reports of log4j2 having deadlock issues, so I think that is fine.

> 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: Rollover, async, daily, features, hourly, rolling
>         Attachments: log4j2-trace.png, 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