You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Jetty logs are not written when we set the log level to "Warning", but able to see logs written when we set Info and Debug level as expected.
Also when we set the jetty log level to "Debug" in one scenario we are getting Warning logs written.
Ex:
Under class org.eclipse.jetty.util.component.AbstractLifecycle.java setFailed(), there is a warning log printed when debug is enabled:
You don't say which logging implementation you are using, is it jetty's StdErrLog or something else? If StdErrLog, then the log level to set is "WARN".
As for the AbstractLifeCycle.setFailed() method you mentioned, there are a few cases where the log level to test of DEBUG has explicitly been chosen, because the exception is not something that you want to see on a regular basis, but reveals maybe some extra detailed information you may be interested in if you're digging deeper into the log levels. So I don't necessarily think this particular case is a problem.
Jetty version
jetty-util-9.4.30.v20200611
Java version
1.8
OS type/version
Linux
Description
Jetty logs are not written when we set the log level to "Warning", but able to see logs written when we set Info and Debug level as expected.
Also when we set the jetty log level to "Debug" in one scenario we are getting Warning logs written.
Ex:
Under class org.eclipse.jetty.util.component.AbstractLifecycle.java setFailed(), there is a warning log printed when debug is enabled:
The text was updated successfully, but these errors were encountered: