-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Logback INFO messages are always reported #33626
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
Comments
This is likely caused by #33610 but those messages should only happen if there's a warning. Do you have a sample application we can run that replicates the problem? |
Hi @philwebb Running the sample app with any profile generates those log messages on startup. |
Was thinking about this and that I had not created a test project yet but I guess I do not have to now.. :) |
Thanks for the sample @pandrez. It looks like in your case the messages are being logged because there is still a warning. If I run the app I see:
That warning is coming from If I change your config to the following: <include resource="org/springframework/boot/logging/logback/defaults.xml"/>
<springProfile name="local">
<include resource="org/springframework/boot/logging/logback/console-appender.xml" />
</springProfile>
<appender name="CONSOLE_JSON" class="ch.qos.logback.core.ConsoleAppender">
... I don't get the warning. |
@bjorntj Does your application have a similar configuration? Are you seeing any |
@philwebb Thank you for your help! I solved the problem by defining the profile-specific appenders inside the Once again, thank you for your support. |
Yes, you are correct.. I had several appenders that wasn't referenced. |
Thanks for letting us know. The improved reporting of problems with the configuration is due to the changes made for #33610. |
Uh oh!
There was an error while loading. Please reload this page.
After upgrading to Spring Boot 3.0.1, I get the following "error" when running my application:
Downgrading to Spring Boot 3.0.0 removes this.
The text was updated successfully, but these errors were encountered: