You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/12/25 13:32:58 UTC
[jira] [Updated] (LOG4J2-1628) Regression in FileAppender locking
since 2.6
[ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma updated LOG4J2-1628:
--------------------------------
Summary: Regression in FileAppender locking since 2.6 (was: Scrambled log messages)
> Regression in FileAppender locking since 2.6
> --------------------------------------------
>
> 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
> Assignee: Remko Popma
>
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org