[
https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15771467#comment-15771467
]
Mark Bowman commented on LOG4J2-1628:
-------------------------------------
Thanks Remko,
I can answer some of these now. Other will take some effort.
* The file is being written to by multiple applications in different JVMs on
multiple hosts. The file is on a shared NFS mount. The file is only accessed
via log4j2. My reading of documentation is that this what locking is designed
to allow (https://logging.apache.org/log4j/2.x/manual/appenders.html)
* Each application will presumably only log via a single thread because I am
using an AsyncLogger, so log4j2 manages the thread doing the actual file access.
* The scrambling is as you describe
* The double class path is correct in this instance (usually the classes are
different parent: child)
> Scrambled log messages
> ----------------------
>
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
