-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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
Application fails to start with excluded health endpoint when JMX is enabled #28131
Comments
@ThomasVitale I was not able to reproduce the behavior with the provided sample. However, if I add |
@mbhave When I run the app I referenced, I get the following error message at startup. If I don't provide any Actuator configuration at all, then the application starts up correctly (even if
|
@mbhave I investigated a bit more and found the following.
I have updated my example app, including an auto test that now fails and shows the error: https://github.com/ThomasVitale/spring-boot-additonal-health-group/blob/main/src/test/java/com/example/demo/DemoApplicationTests.java |
@ThomasVitale Thanks, this was the behavior that I observed as well. |
Starting from Spring Boot 2.6.0-M2, the Spring Boot Actuator fails during the application startup when the
health
endpoint is not included in themanagement.endpoints.web.exposure.include
property. It looks like that scenario triggers Actuator to use the new functionality added in #25471 for supporting additional health endpoint paths, even if no configuration has been provided for that.It's probably not that common to use Actuator without leveraging the useful
health
endpoint, but if that happens, it's a breaking issue when upgrading to Spring Boot 2.6.0+ (the error is not present in 2.5.5).I made a small demo application you can run and see more details in the logs about the error thrown during the startup. https://github.com/ThomasVitale/spring-boot-additonal-health-group
An extract of the error message:
The text was updated successfully, but these errors were encountered: