-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Not able to monitor Spring Boot 1.x components after upgrading to 2.4.0 #1638
Comments
we had the same message in #1631 |
Thank you for the hint. Spring Boot Admin is using In case the response is using Everything works perfectly only with |
Thanks for providing the additional info. Can you provide a sample app which reproduces the issue. FYI - @codecentric/spring-boot-admins |
applications.zip contatins six applications. Four applications are simple Spring Boot applications without security, exposing
Besides them, there are two versions of Spring Boot Admin:
Both of them are configured to monitor all four Spring Boot applications, using a static configuration with Additionally, I wrote the test to check is Spring Boot Admin registers mocked versions of applications (
The last scenario is not a real-life scenario because Spring Boot admin uses the Test scenarios that are failing are disabled. |
may be the IllegalStateException is due to reactor/reactor-netty#1513 ? |
That one is pointing to spring-cloud/spring-cloud-sleuth/issues#1854, but there is no Spring Cloud Sleuth in the provided example. |
The issue is also reproducible with Spring Boot v2.4.4. |
After upgrading to Spring Boot 2.4.x `LegacyEndpointConverter` was never called. Switching to the `ClientResponse` builder method, which transforms the existing body directly, instead of changing the body and setting it in two steps, solves the problem.
…-relpaths * origin/master: Add retry on failing subscription (codecentric#1697) chore(deps): update dependency pl.project13.maven:git-commit-id-plugin to v4.0.4 (codecentric#1663) chore(deps): update dependency com.puppycrawl.tools:checkstyle to v8.41.1 (codecentric#1648) Fix for codecentric#1638 (codecentric#1673) Improve npm ci build times (see codecentric#1688) (codecentric#1689) Improved execution of grouped assertions (codecentric#1674) Use maven repo cache during publish snapshots (codecentric#1687) chore(deps): update metcalfc/changelog-generator action to v1 (codecentric#1669) chore(deps): update dependency org.codehaus.mojo:flatten-maven-plugin to v1.2.7 (codecentric#1686) Fix file formating by applying spring-javaformat:apply (codecentric#1685) Cache mvn repo in main build (see codecentric#1677 ) (codecentric#1678) Added support DingTalk notifier. (codecentric#1653) Simplify some code (codecentric#1670) Bugfix/1646 (codecentric#1661) Upgrade spring cloud dependencies (codecentric#1645) chore(deps): update dependency com.github.eirslett:frontend-maven-plugin to v1.11.2 (codecentric#1635) chore(deps): update spring boot to v2.4.3 (codecentric#1637) Bump version to 2.4.1-SNAPSHOT chore(deps): update testcontainers.version to v1.15.2 (codecentric#1629)
After upgrading to Spring Boot Admin 2.4.0 and Spring Boot 2.4.2, I am getting the following error when Spring Boot Admin is updating the status of a monitored component:
The monitored component is responding correctly on health and info actuator endpoints.
Everything was working with Spring Boot Admin 2.3.1 and Spring Boot 2.3.6.RELEASE.
The text was updated successfully, but these errors were encountered: