You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Spring Boot 3.3x and AMQP 3.2.0 one can write cachingConnectionFactory.setAddresses(rabbitProperties.getAddresses()); which is impossible with 3.4.0
Expected behavior
Either make setAddresses compatible with the new RabbitProperties or add a new method that is.
The text was updated successfully, but these errors were encountered:
Not sure why would one use Spring Boot, but not its auto-configuration.
I mean that CachingConnectionFactory bean is really created by the RabbitAutoConfiguration, so no need to deal with your own custom beans.
As a workaround I see that it is easy to adjust your code:
In what version(s) of Spring AMQP are you seeing this issue?
3.2.0
Describe the bug
In Spring Boot 3.4.0 org.springframework.boot.autoconfigure.amqp.RabbitProperties#getAddresses() returns a
List<String>
while it previously returned aString
.This makes it incompatible with AbstractConnectionFactory.setAddresses which accepts a String.
With Spring Boot 3.3x and AMQP 3.2.0 one can write
cachingConnectionFactory.setAddresses(rabbitProperties.getAddresses());
which is impossible with 3.4.0Expected behavior
Either make
setAddresses
compatible with the new RabbitProperties or add a new method that is.The text was updated successfully, but these errors were encountered: