logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1628) File locking regression for Async FileAppender
Date Fri, 30 Sep 2016 23:35:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537413#comment-15537413

Remko Popma commented on LOG4J2-1628:

Mark, the problem description of scrambled messages reminded me of LOG4J2-1583, which was
tracked down to the objects being logged themselves doing logging from their {{toString()}}
method, which didn't play well with some of the mechanisms used to make Log4j garbage-free.

That issue has been fixed. Can you try if the problem still occurs with our current master?

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message