[
https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549505#comment-15549505
]
Mark Bowman commented on LOG4J2-1628:
-------------------------------------
That's actually quite a big ask. The LCOGTLayout formats the messages to be
ingested into ElasticSearch. Kibana makes searching for these (very) rare
events very easy. If I was to dump the data to file using a Patternlayout I'm
not entirely sure I would be able to prove one way or another if the problem
exists.
I'll have a ponder.
> 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]
