LOG4J2-2965: Fix JUL/AsyncLoggerContext deadlock
diff --git a/pom.xml b/pom.xml
index ca5dc58..f82bfce 100644
--- a/pom.xml
+++ b/pom.xml
@@ -193,7 +193,7 @@
<springVersion>5.3.2</springVersion>
<kubernetes-client.version>4.6.1</kubernetes-client.version>
<flumeVersion>1.9.0</flumeVersion>
- <disruptorVersion>3.4.2</disruptorVersion>
+ <disruptorVersion>3.4.4</disruptorVersion>
<conversantDisruptorVersion>1.2.15</conversantDisruptorVersion>
<elastic.version>7.6.2</elastic.version>
<mongodb3.version>3.12.4</mongodb3.version>
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 4964ba2..1f4f835 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -214,6 +214,9 @@
<action issue="LOG4J2-2940" dev="ckozak" type="fix">
Slf4j implementations walk the stack at most once rather than twice to determine the caller's class loader.
</action>
+ <action issue="LOG4J2-2965" dev="ckozak" type="fix">
+ Fixed a deadlock between the AsyncLoggerContextSelector and java.util.logging.LogManager by updating Disruptor to 3.4.4.
+ </action>
<!-- UPDATES -->
<action dev="ggregory" type="update">
- org.eclipse.persistence:javax.persistence ............. 2.1.1 -> 2.2.1
