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
Resolves#1289
`RoutingConnectionFactory` did not support correlated confirms or returns.
Target factories (and default) must have the same settings.
**cherry-pick to 2.2.x, 2.1.x**
Copy file name to clipboardExpand all lines: spring-rabbit/src/main/java/org/springframework/amqp/rabbit/connection/AbstractRoutingConnectionFactory.java
+39-3Lines changed: 39 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
/*
2
-
* Copyright 2002-2019 the original author or authors.
2
+
* Copyright 2002-2020 the original author or authors.
3
3
*
4
4
* Licensed under the Apache License, Version 2.0 (the "License");
5
5
* you may not use this file except in compliance with the License.
Copy file name to clipboardExpand all lines: spring-rabbit/src/test/java/org/springframework/amqp/rabbit/core/RabbitTemplatePublisherCallbacksIntegrationTests2.java
+56-7Lines changed: 56 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
/*
2
-
* Copyright 2016-2019 the original author or authors.
2
+
* Copyright 2016-2020 the original author or authors.
3
3
*
4
4
* Licensed under the Apache License, Version 2.0 (the "License");
5
5
* you may not use this file except in compliance with the License.
Copy file name to clipboardExpand all lines: src/reference/asciidoc/amqp.adoc
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -691,6 +691,9 @@ Doing so enables, for example, listening to queues with the same name but in a d
691
691
692
692
For example, with lookup key qualifier `thing1` and a container listening to queue `thing2`, the lookup key you could register the target connection factory with could be `thing1[thing2]`.
693
693
694
+
IMPORTANT: The target (and default, if provided) connection factories must have the same settings for publisher confirms and returns.
695
+
See <<cf-pub-conf-ret>>.
696
+
694
697
[[queue-affinity]]
695
698
===== Queue Affinity and the `LocalizedQueueConnectionFactory`
696
699
@@ -1196,7 +1199,7 @@ The reason is not populated for broker-generated `nack` instances.
1196
1199
It is populated for `nack` instances generated by the framework (for example, closing the connection while `ack` instances are outstanding).
1197
1200
1198
1201
In addition, when both confirms and returns are enabled, the `CorrelationData` is populated with the returned message, as long as the `CorrelationData` has a unique `id`; this is always the case, by default, starting with version 2.3.
1199
-
It is guaranteed that the return message is set before the future is set with the `ack`.
1202
+
It is guaranteed that the returned message is set before the future is set with the `ack`.
1200
1203
1201
1204
See also <<scoped-operations>> for a simpler mechanism for waiting for publisher confirms.
0 commit comments