Hi Gary, On 3.02.2025 19:51, Gary Gregory wrote:
Do you think it's possible to add a test to avoid regressions?
It is hard to reproduce the problem in a test. There are actually two problems:
1. Something happens during the creation of a new logger that stops the process in some environments until some other lock is acquired. Since there are many customizable Log4j elements like property sources, we never found out what it is, we just corrected the problem of one user and he confirmed it is solved.
2. Due to a bug in `InternalLoggerRegistry`, the registry cached only the first instance of a given `Logger`. If that logger was GC-ed, all requests for a new logger of that name created a new logger. We could add a benchmark for that, but we don't have a framework to test for performance regressions.
Piotr
