tristantarrant commented on issue #3399: URL: https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2623800127
I have some good news: combining the fix in https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2622418350 with my fix in https://github.com/tristantarrant/infinispan/tree/log4j-lock-investigation seems to allow our core testsuite to complete. I think the reason why just the fix in log4j wasn't enough is because of resource starvation: our testsuite has lots of parallelism with tons of lock contention, many threads, GCs. Still, I want to investigate a bit further. JGroups (one of the libraries we use) still creates per-instance loggers: I'll create a PR to fix that today. -- 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
