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
Copy file name to clipboardExpand all lines: src/reference/asciidoc/whats-new.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ The `RabbitConnectionFactoryBean` now calls `enableHostnameVerification()` by de
84
84
The `CachingConnectionFactory` now unconditionally disables auto recovery in the underlying RabbitMQ `ConnectionFactory`, even if a pre-configured instance is provided in a constructor.
85
85
While steps have been taken to make Spring AMQP compatible with auto recovery, certain corner cases have arisen where issues remain.
86
86
Spring AMQP has had its own recovery mechanism since 1.0.0 and doesn't need to use the recovery provided by the client.
87
-
While it is still possible to enable the feature (using `cachingConnectionFactory.getRabbitConnectionFactory().setAutomaticRecoveryEnabled()`) after the `CachingConnectionFactory` is constructed, it is **strongly recommended that you not do so**.
87
+
While it is still possible to enable the feature (using `cachingConnectionFactory.getRabbitConnectionFactory()` `.setAutomaticRecoveryEnabled()`) after the `CachingConnectionFactory` is constructed, it is **strongly recommended that you not do so**.
88
88
Use a separate RabbitMQ `ConnectionFactory` if you need auto recovery connections when using the client factory directly (rather than via Spring AMQP components).
0 commit comments