ppkarwasz commented on issue #3282: URL: https://github.com/apache/logging-log4j2/issues/3282#issuecomment-2524161891
> The loadClass method is called internally within Log4j. I wonder if there should be some mechanism that can monitor and alert users when too many different classes have been loaded, making this problem easier to expose. As mentioned by @vy, in `2.25.0` the `ThrowableProxy` class will no longer be used. The code that determines the additional packaging information for each class is now in [`ThrowableExtendedStackTraceRenderer`](https://github.com/apache/logging-log4j2/blob/2.x/log4j-core/src/main/java/org/apache/logging/log4j/core/pattern/ThrowableExtendedStackTraceRenderer.java). We could probably: - enhance it to skip the generation of packaging information for classes in the `ignoredPackages` option. - you could then specify `%xEx(filters=jdk.nashorn.internal.scripts)` to ignore the packaging information of the classes generated by Nashorn. -- 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
