|
This version is still in development and is not considered stable yet. For the latest stable version, please use Spring AMQP 4.1.2! |
What’s New
Changes in 4.2 Since 4.1
TLS Hostname Verification
The RabbitConnectionFactoryBean#setEnableHostnameVerification(boolean) is deprecated now.
Since amqp-client 5.33, hostname verification is enabled automatically whenever TLS is configured through useSslProtocol.
See Connection and Resource Management for more information.
For the same reason, the verifyHostname property on the Logback and Log4j 2 AmqpAppender s is also deprecated now.
See Logging Subsystem AMQP Appenders for more information.
Declaring Several Objects at Once
The AmqpAdmin now has declareExchanges(), declareQueues() and declareBindings() methods to declare several objects in one call; the RabbitAdmin declares them on a single channel.
See Configuring the Broker for more information.
@RabbitListener Batch Overrides
The @RabbitListener annotation has new batchSize() and batchReceiveTimeout() attributes to override the respective container factory properties for a single listener.
See @RabbitListener with Batching for more information.
Routing AMQP Connection Factory
The spring-rabbitmq-client module now provides an AbstractRoutingAmqpConnectionFactory (and a SimpleRoutingAmqpConnectionFactory implementation) to route to one of several AmqpConnectionFactory instances based on a runtime lookupKey.
See Routing Connection Factory for more information.
RestClientNodeLocator
A new RestClientNodeLocator is now the default non-reactive NodeLocator implementation for the LocalizedQueueConnectionFactory.
The RestTemplateNodeLocator is deprecated since the RestTemplate is deprecated in Spring Framework 7.1.
See Queue Affinity and the LocalizedQueueConnectionFactory for more information.
RetryListener on Stateless Retry Interceptor
The StatelessRetryOperationsInterceptor (and its StatelessRetryOperationsInterceptorFactoryBean) now supports registering a RetryListener .
See Failures in Synchronous Operations and Options for Retry for more information.
Observation for Listener Replies
Listener replies now automatically inherit and propagate observation trace context when observation is enabled on the listener container. See Micrometer Observation for more information.