From 430f0bf07d00c4ef7acab0c989881a0d85b64cb3 Mon Sep 17 00:00:00 2001 From: Gary Russell Date: Wed, 10 Nov 2021 11:28:33 -0500 Subject: [PATCH] GH-1099: Fix Javadocs for Publisher Connection Resolves https://github.com/spring-projects/spring-amqp/issues/1099 **cherry-pick to 2.3.x, 2.2.x** --- .../amqp/rabbit/core/RabbitTemplate.java | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/core/RabbitTemplate.java b/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/core/RabbitTemplate.java index 900d0b0b..652c0c63 100644 --- a/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/core/RabbitTemplate.java +++ b/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/core/RabbitTemplate.java @@ -823,10 +823,12 @@ public class RabbitTemplate extends RabbitAccessor // NOSONAR type line count } /** - * To avoid deadlocked connections, it is generally recommended to use - * a separate connection for publishers and consumers (except when a publisher - * is participating in a consumer transaction). Default 'false'; will change - * to 'true' in 2.1. + * To avoid deadlocked connections, it is generally recommended to use a separate + * connection for publishers and consumers (except when a publisher is participating + * in a consumer transaction). Default 'false'. When setting this to true, be careful + * in that a {@link RabbitAdmin} that uses this template will declare queues on the + * publisher connection; this may not be what you expect, especially with exclusive + * queues that might be consumed in this application. * @param usePublisherConnection true to use a publisher connection. * @since 2.0.2 */