plusterkopp commented on issue #4356: URL: https://github.com/apache/logging-log4j2/issues/4356#issuecomment-5998740638
With the snapshot from last weekend, I see no discarded events. Instead, there are 30 worker threads Name: Log4j2-TF-11-RollingFileManager-11/WAITING, T: 0.000ms/15.625ms, R: 0.0%/0.0%, B: 0.0%/0.0%, W: 0.0%/0.0%, Priority: 5, in: Unsafe.park(Native Method), LockSupport.park(LockSupport.java:369), AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:520), ForkJoinPool.unmanagedBlock(ForkJoinPool.java:4364), ForkJoinPool.managedBlock(ForkJoinPool.java:4310), AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1752), ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1154), ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:883), ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1016), ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076), ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614), Thread.runWith(Thread.java:1487), Thread.run(Thread.java:1474) Count starts at 2, so there may have been a number 1 that has finished. Should I try 2.26.2? If so, how do I invoke maven to also build source jars? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
