[
https://issues.apache.org/jira/browse/LOG4J2-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207770#comment-16207770
]
ASF subversion and git services commented on LOG4J2-2078:
---------------------------------------------------------
Commit 247c91d01cb4563cc4615eafd81fff5133b44b84 in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=247c91d ]
[LOG4J2-2078] Update LMAX disruptor from 3.3.6 to 3.3.7. Note that in
order to get a passing build with 'mvn clean install' I had to revert in
the previous commit the changes for LOG4J2-2060 AbstractDatabaseManager
should make a copy of LogEvents before holding references to them:
AsyncLogger log events are mutable.
> Update LMAX disruptor from 3.3.6 to 3.3.7
> -----------------------------------------
>
> Key: LOG4J2-2078
> URL: https://issues.apache.org/jira/browse/LOG4J2-2078
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.9.1
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.10.0
>
>
> Update LMAX disruptor from 3.3.6 to 3.3.7.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
