[ 
https://issues.apache.org/jira/browse/LOG4J2-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Gregory resolved LOG4J2-296.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta8
         Assignee: Gary Gregory

Thank you for the patch.
{noformat}
commit -m "[LOG4J2-296] Wasted work in FlumePersistentManager.createManager." 
C:/vcs/svn/apache/log4j2/trunk/src/changes/changes.xml 
C:/vcs/svn/apache/log4j2/trunk/flume-ng/src/main/java/org/apache/logging/log4j/flume/appender/FlumePersistentManager.java
    Sending        
C:/vcs/svn/apache/log4j2/trunk/flume-ng/src/main/java/org/apache/logging/log4j/flume/appender/FlumePersistentManager.java
    Sending        C:/vcs/svn/apache/log4j2/trunk/src/changes/changes.xml
    Transmitting file data ...
    Committed revision 1498789.
{noformat}

                
> Wasted work in FlumePersistentManager.createManager
> ---------------------------------------------------
>
>                 Key: LOG4J2-296
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-296
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Flume Appender
>    Affects Versions: 2.0-beta7
>         Environment: any
>            Reporter: Adrian Nistor
>            Assignee: Gary Gregory
>              Labels: patch, performance
>             Fix For: 2.0-beta8
>
>         Attachments: patch.diff
>
>
> The problem appears in Log4j 2.0-beta7 and in revision 1497930.  I
> attached a one-line patch that fixes it.
> In method "FlumePersistentManager.createManager", the loop over
> "properties.entrySet()" should break immediately after "key" is set
> the first time to "entry.getValue()".  I don't think "key" is set a
> second time (and therefore all future iterations are not useful), but
> if it is, then there is a problem in the implementation: when the loop
> exits, "key" would be set to the last value of "entry.getValue()" that
> meets some condition; however "properties.entrySet()" is a Set and
> therefore the order of iterating it is non-deterministic, i.e., the
> implementation should not rely on which the "last value" is.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to