shloim

> Alternatively, can you upgrade your Log4j version to 2.18.0 or later? > > In 2.18.0 @remkop backported the `TimeoutBlockingWaitStrategy` from Disruptor 4.x with such a comment: > > https://github.com/apache/logging-log4j2/blob/252f1a65e1b44fa78c622b4140d9116bf57d3617/log4j-core/src/main/java/org/apache/logging/log4j/core/async/TimeoutBlockingWaitStrategy.java#L34-L40...

After switching to log4j 2.18.0 the issue persists but in a different stacktrace: ``` "Log4j2-TF-1-AsyncLogger[AsyncContext@46f5f779]-1" #20 daemon prio=5 os_prio=0 cpu=3228328.37ms elapsed=3495.56s tid=0x00007fea233e9000 nid=0xd0 runnable [0x00007fea23dfd000] java.lang.Thread.State: RUNNABLE at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:159) at...