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
Numerous logs mentioning a failed JNDI lookup when using Jetty #22241
Comments
This does not seem to be related to the core framework so I've moved this issue to Spring Boot. It sounds like you're reporting an upgrade problem but you didn't mention the version of Spring Boot that you were using previously that didn't have the problem. If you revert to this version without changing anything else (including the Spring Cloud version), are those logs going away? |
Thanks for the reply. I had initially created the issue in the main Spring tracker as the We migrated from Spring Boot Edit: FWIW, we also updated from Spring Cloud Stream |
There was an issue with Jetty JNDI being enabled by default in Spring Boot 1.X and it was fixed here - #4710.
The issue is not present in Spring Boot 2.1.0.RELEASE and is present in 2.3.1.RELEASE (I know the distance between the versions is long...).
And in 2.3.1:
|
@silh thank you very much for the great detective work. We'll review dependency management and see what we can do to avoid that in the future. |
From a quick look, it looks like a regression of us moving to Gradle. |
Affects: 5.2.7.RELEASE
After migrating to Spring Boot
2.3.1.RELEASE
/ Spring5.2.7.RELEASE
, I am seeing the followingDEBUG
logs upon application startup (in fact, they are the very first log messages printed out):In my
bootstrap.yaml
I have the following:This does not seem to affect my application at all, seeing how we do not use JNDI. However, I have been unable to turn these messages off and I am even surprised that they are logged at all (seeing how the
root
logger is set toINFO
). The fact that it is trying to do a JNDI lookup forlogging.level
makes me think that this is some standard logging that is enabled in Spring itself, before Logback configuration has even been picked up.The text was updated successfully, but these errors were encountered: