File tree Expand file tree Collapse file tree 1 file changed +1
-1
lines changed Expand file tree Collapse file tree 1 file changed +1
-1
lines changed Original file line number Diff line number Diff line change @@ -745,7 +745,7 @@ See <<cf-pub-conf-ret>> for more information about ensuring message delivery.
745
745
When using HA queues in a cluster, for the best performance, you may want to connect to the physical broker
746
746
where the lead queue resides.
747
747
The `CachingConnectionFactory` can be configured with multiple broker addresses.
748
- This is to fail over and the client attempts to connect in order.
748
+ This is to fail over and the client attempts to connect in accordance with the configured `AddressShuffleMode` order.
749
749
The `LocalizedQueueConnectionFactory` uses the REST API provided by the management plugin to determine which node is the lead for the queue.
750
750
It then creates (or retrieves from a cache) a `CachingConnectionFactory` that connects to just that node.
751
751
If the connection fails, the new lead node is determined and the consumer connects to it.
You can’t perform that action at this time.
0 commit comments