[
https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766776#comment-15766776
]
Remko Popma commented on LOG4J2-1628:
-------------------------------------
[~markbowman] I want to take another look at this. To summarize my
understanding (please correct if I'm wrong):
* This is a single process (there are no multiple applications or web apps
writing to the same file)
* The application has multiple threads that log concurrently
* Messages appear scrambled in the log. Example *actual*
{code}
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"}
{code}
*Expected*
{code}
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"}
2016-10-04 23:49:02.741 INFO: org.lcogt.jTCS.jTpoint.TpointAgent:
org.lcogt.jTCS.jTpoint.TpointAgent XXxxxxx behaviour: 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"}
{code}
* I notice that the logger name {{org.lcogt.jTCS.jTpoint.TpointAgent}} appears
twice. Is that expected behaviour?
* Does the problem also occur when you use plain {{Logger}} in the
configuration instead of {{AsyncLogger}}?
* Is it possible to provide a small program that reproduces the issue?
> 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
