Skip to content

Tag LOG4J as origin of WARNING messages and use stderr instead of stdout #1761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

Flowdalic
Copy link
Contributor

The "WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance." gets a lot of attention [1]. Sometimes users are confused about its origin. Therefore identify LOG4J as the originator of the warning.

1: https://www.google.com/search?q=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.&oq=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.

The "WARNING: sun.reflect.Reflection.getCallerClass is not
supported. This will impact performance." gets a lot of attention
[1]. Sometimes users are confused about its origin. Therefore identify
LOG4J as the originator of the warning.

1: https://www.google.com/search?q=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.&oq=WARNING%3A+sun.reflect.Reflection.getCallerClass+is+not+supported.+This+will+impact+performance.
@ppkarwasz
Copy link
Contributor

I close this in favor of #1760.

@ppkarwasz ppkarwasz closed this Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants