-
Notifications
You must be signed in to change notification settings - Fork 179
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
spring-cloud-starter-bus-amqp conflicts with SpringApplicationAdminJmxAutoConfiguration #62
Comments
This is the full contents of the pom.xml as generated by initializr app. https://gist.github.com/kdvolder/55e0f196f5db378cb43c698300022714 |
This appears to be some kind of conflict with the When I disable these JMX related features in STS then the error goes away. (This however results in some loss of functionality in STS boot dashboard). Any idea on how the spring-boot life-cycle management MBeans can be made to play nicely together with |
You'd have to get in touch with the STS and/or Spring Boot team. My guess is that you'd have the problem even without amqp if you had a plain integration app. |
Thanks, but I'm actually on the STS team :-) We need that 'admin' JMX bean which spring-boot provides. I'm trying to figure out who/why these other beans are getting turned on and who to talk to about figuriing out some kind of a solution to this conflict (other than just disabling a bunch of STS functionality to avoid it). But I guess this problem isn't from the starter itselff but one part of spring-boot conflicting with another part of spring-boot (i.e. not a spring-cloud-specific problem)? |
Sorry for not recognizing you Kris. I didn't get your previous message when I had written mine. The bus pulls in |
Closed in favor of spring-projects/spring-boot#6328. Thank you for spotting such a nasty regression. The only problem was that we don't have enough test coverage. But will we have it anyway ever?.. 😄 |
I created a project with spring-initializr and added just a single starter.
This added this:
and this:
to my pom (I'll attach full pom as well later).
I guess that seems okay and as expected.
When I run this empty app however it crashes with some nasty error about failing to create JMX releated bean.
I was expecting the empty app to not do anything, or, perhaps crash with some error for not being able to connect to rabbitmq unsintance until I install and configure it somehow. I was not expecting a problem with JMX beans.
Not sure who this error should be blamed on. Is it initializer not generating proper pom? Is it the
spring-cloud-starter-bus-amqp
? Something else?I just made my best guess and raised this against 'spring-cloud-starters' as I don't get this with other starters so I'm inclined to blame the starter for this.
The text was updated successfully, but these errors were encountered: