ppkarwasz commented on PR #2768: URL: https://github.com/apache/logging-log4j2/pull/2768#issuecomment-2250452028
> Again, we're not using LoaderUtil. This is also not in Graal (Graal doesn't yet support agents, and when it does it won't have this kind of issue because it flattens classloading) Sorry, I am not referring to the code of your application, but these lines in Log4j Core: https://github.com/apache/logging-log4j2/blob/2d5f5828e6996ac330695ad35f2a713372d895d2/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerDisruptor.java#L56-L60 I think that line 57 constitutes the problem, since it might load the `RingBufferLogEventHandler` class from a different classloader than the one that loaded `AsyncLoggerDisruptor`. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
