ppkarwasz commented on issue #3399: URL: https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2616804588
> Is this helpful and understandable? If this does not get you any further I will invest some time to try and build a reproducable example that I can share. It is very clear thanks. We have already seen some unwanted effects if `LoggerContext.newInstance` has a complex logic (e.g. #3252). Probably we should rewrite `computeIfAbsent`, so that logger creation occurs without any locks: 1. (under read lock) We check if the logger already exists. 2. We create the logger. 3. (under write lock) We add the logger to the repository. Since all loggers with the same name are equivalent, we don't need to ensure that the logger is created only once. @vy, what do you think? -- 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
