[
https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537468#comment-15537468
]
Mark Bowman commented on LOG4J2-1628:
-------------------------------------
The core module of log4j2 master doesn't build for me.
Failed tests:
JeroMqAppenderTest.testClientServer:54 Appender named JeroMQAppender was null
in logger context org.apache.logging.log4j.core.LoggerContext@724af044
JeroMqAppenderTest.testMultiThreadedServer:81 Appender named JeroMQAppender
was null in logger context org.apache.logging.log4j.core.LoggerContext@724af044
JeroMqAppenderTest.testServerOnly:129 Appender named JeroMQAppender was null
in logger context org.apache.logging.log4j.core.LoggerContext@724af044
> File locking regression for Async FileAppender
> ----------------------------------------------
>
> Key: LOG4J2-1628
> URL: https://issues.apache.org/jira/browse/LOG4J2-1628
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.6.2
> Environment: centos
> Reporter: Mark Bowman
>
> We have several threads writing to an async file with locking set to true.
> Under log4j 2.5 the message from each thread are interleaved correctly. Using
> log4j 2.6.2 some messages are scrambled as if multiple threads are writing to
> the file simultaneously. Reverting to 2.5 fixes the problem.
> Configuration to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
