[
https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549475#comment-15549475
]
Mark Bowman commented on LOG4J2-1628:
-------------------------------------
Just to be clear the problem is not out-of-order messages, it is messages
scrambled (presumably) due to simultaneous file access. For example, the second
message below has lost the first few dozen characters
{noformat}
2016-10-04 23:49:02.741 INFO: org.lcogt.jTCS.jTpoint.TpointAgent:
org.lcogt.jTCS.jTpoint.TpointAgent: Setting pier adjustment: Lower
tail-fixator:0.4mm, Shift front-rail East:0.6mm |
{"observatory":"aqwa","path":"0m4a.aqwa.lsc","agent":"Tpoint","site":"lsc","telescope":"0m4a"}
viour: Exposure time is 10.0 and exp time factor 1.0 |
{"observatory":"domc","path":"ef08","site":"lsc","agent":"ef08","tracking_num":"0000238128","request_num":"0000795735","molecule_id":"236030862","telescope":"1m0a","block_id":"95121483"}
{noformat}
> 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]
