Skip to content
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

java.lang.System logging is not routed to Quarkus logging #33109

Closed
rvansa opened this issue May 3, 2023 · 1 comment · Fixed by #33318
Closed

java.lang.System logging is not routed to Quarkus logging #33109

rvansa opened this issue May 3, 2023 · 1 comment · Fixed by #33318
Labels
area/logging kind/bug Something isn't working
Milestone

Comments

@rvansa
Copy link
Contributor

rvansa commented May 3, 2023

Describe the bug

When JDK logs using System.Logger:

    public static final System.Logger logger = System.getLogger("foo.bar");
    public static void debug(String fmt, Object... params) {
        logger.log(System.Logger.Level.DEBUG, fmt, params);
    }

even though Quarkus is built with -Dquarkus.log.min-level=TRACE and ran with -Dquarkus.log.level=TRACE -Dquarkus.log.console.level=TRACE these message are not printed out.

Expected behavior

Quarkus logs this at DEBUG level.

Actual behavior

Logs from within Quarkus systems are correctly printed but System logging is not printed anywhere.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

OpenJDK CRaC build

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.15.3.Final

Build tool (ie. output of mvnw --version or gradlew --version)

Maven

Additional information

No response

@rvansa rvansa added the kind/bug Something isn't working label May 3, 2023
@rvansa
Copy link
Contributor Author

rvansa commented May 3, 2023

@dmlloyd Please have a look. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logging kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants