-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Verbose and unhelpful logging with Boot + Jetty if context fails to load #3026
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
Labels
Comments
With Spring Boot 1.5, Jetty's warn-level logging still occurs (and we can't do much about that), but Boot now performs failure analysis. This results in the following output:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
We have a standard configuration for Spring Boot across a number of projects. If a developer makes a mistake in configuration, we have found the logging output to be difficult to work with. The example linked below demonstrates a mistake in a very simple Spring context configuration. It results in 340 lines of errors logged, much of it redundant log output. Actual use cases involve much richer context configuration, making the output much longer and harder to read.
The problem comes from redundant logging statements across Jetty, Spring, and Boot.
Because of that, this issue is being filed without a lot of hope for resolution.
But I thought I would raise attention to it anyway as it represents a usability problem for what otherwise is a great development environment.
Reproducer
An example Spring Boot project that demonstrates the problem is available here:
Workaround
logback.xml can be configured like the following, which suppresses all logging from the contributing classes:
Configuration
Logging Code Points
The context creation exceptions bounce up the call stack, logging out at these locations (module:class:line):
The text was updated successfully, but these errors were encountered: