You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/02/16 00:29:00 UTC

[jira] [Commented] (LOG4J2-2782) Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration

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

ASF subversion and git services commented on LOG4J2-2782:
---------------------------------------------------------

Commit b74f92cbf1e7107b0ef637f252d752b1470c7aee in logging-log4j2's branch refs/heads/master from Ralph Goers
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=b74f92c ]

LOG4J2-2782 - Use LinkedBlockingQueue instead of synchronous collection


> Use LinkedBlockingQueue instead of synchronized collection in StatusConfiguration
> ---------------------------------------------------------------------------------
>
>                 Key: LOG4J2-2782
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2782
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.13.0
>            Reporter: Ralph Goers
>            Priority: Major
>             Fix For: 2.13.1
>
>
> StatusConfiguration uses a synchronized collection but then iterates over it without synchronizing. Using a class from java.util.concurrent would solve this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)