[
https://issues.apache.org/jira/browse/LOG4J2-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161631#comment-16161631
]
Colin McDowell commented on LOG4J2-2031:
----------------------------------------
Hi Remko,
Not sure if our are directing all these comments in my direction. I did little
more testing with v2.8.2 and v2.9.0.
I created a log4j2.component.properties
containinglog4j2.AsyncQueueFullPolicy=com.allstate.drivewise.logger.log4j2.BlockingAsyncQueueFullPolicy
AsyncLoggerConfig.RingBufferSize=8096
Also
public class BlockingAsyncQueueFullPolicy implements AsyncQueueFullPolicy {
@Override
public EventRoute getRoute(long arg0, Level arg1) {
return EventRoute.ENQUEUE;
}
}
With the above config the test logging 180,000 entries the test is both fast
and the ordering problem is fixed.
Still this toString() deadlock issue is worrying. We use many many open source
libraries. How could I guarantee none of them is logging in any of their
toString functions.
If I take the log4j2.AsyncQueueFullPolicy out then the ordering problems
returns. Also the AsyncLoggerConfig.RingBufferSize appears have no affect. The
unordered entries appear in the same place. I would have expected increasing
the queue size to have a positive effect.
I don't follow the information regarding handling the Background thread.
Obviously I don't know the Log4j2 source code.
> Messages appear out of order in log file (was: Log4j2 log file not reflecting
> application log function calls)
> -------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2031
> URL: https://issues.apache.org/jira/browse/LOG4J2-2031
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.8.2, 2.9.0
> Environment: Windows, Sun Java 8.
> Reporter: Colin McDowell
> Assignee: Remko Popma
> Attachments: CapacityTest.java, log4j2.xml, pom2.xml
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Was hoping to move our numerous J2EE projects from Log4j to Log4j2 for the
> performance improvements. I put together a small test case that writes a
> string pattern to a Rolling File. There is a 6 digit sequence number at the
> start of the log message. This allows me to quickly see if all the log
> requests are making it into the log file. I attach the test case and
> log4j2.xml. The log4j2.xml uses an asynchronous appender.
> What I observe in the output log file is that after a short interval (120 or
> so entries) the logged are appearing in the wrong order, and entries can be
> missing. The missing entries issues especially shows up when rolling to the
> next log file.
> Perhaps there is a deliberate decision to not to guarantee log file
> accurately for speed. However we need the logs to accurately reflect what
> the application is logging. I have also noticed the performance is 25% worse
> in Log4j2 than Log4j when not using the asynchronous appender. So that
> rather kills us using Log4j2 at the moment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
