-
Notifications
You must be signed in to change notification settings - Fork 41k
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
when upgrading from 3.4.3 to 3.4.4 the dbHealthContributor suddenly tries to add integration MessageChannel #44873
Comments
If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I am trying to reduce the configuration and code to create a minimal sample project but so far I was not able to reproduce it outside of our project |
I was able to fix my integration configuration. It seems like not explicetely defining the input channel used in This worked before:
Now I need to add
I have to look into changes in Spring Integration to figure out why this suddenly changed ... |
Thanks for the follow up. I don't think it's a change in Spring Integration that's triggered it. The use of CCing @artembilan to see if there's anything that could be tweaked on the Spring Integration side to remove the need for the explicit channel declaration. |
The XML parser for that
That one contributes to the
So, apparently this one is not
Does that make sense? Thanks |
Defining beans in |
Thanks for confirmation, Andy! Must not be a problem because that one is just this:
So, no any other dependencies. Although I might rework it into a Spring Integration issue: spring-projects/spring-integration#9931 |
I am trying to upgrade from 3.4.3 to 3.4.4 but some of my tests fail with the following stacktrace:
why do the actuator health endpoints/probes suddenly try add Spring Integration channels to their checks?
The text was updated successfully, but these errors were encountered: