vy commented on issue #3399: URL: https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2594674923
@nilsson-petter, thanks so much for the report. It indeed appears like a bug. 1. `<0x00000000e01f0be0>` points to the read-lock of a read-write-lock. The associated write-lock is acquired only at one place: `InternalLoggerRegistry#computeIfAbsent()`. Do you happen to see any references to that in your thread dump? 2. Would you mind providing the complete thread dump, please? -- 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: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
