freelon commented on issue #3399: URL: https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2612268508
I am stumbling upon (probably) the same problem and can reliably reproduce it. I could share stack traces if that helps, but sadly I cannot hand out a minimal example because we are using an internal library in our setup. Our setup reads from a zookeeper instance which log levels are configured, but the classes that do that contain loggers themselves. Until now this wasn't a problem. I suspect that due to the changes in locking between `LoggerRegistry` and `InternalLoggerRegistry` the thread that receives the answer from zookeeper is blocked trying to obtain its logger. -- 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
