From f09f4563d929c90fbd7f6c37df506558ce9f0951 Mon Sep 17 00:00:00 2001
From: Artem Bilan <abilan@pivotal.io>
Date: Mon, 23 Oct 2017 10:35:54 -0400
Subject: [PATCH] Use `cacheConsumers=false` for  CachingJmsCF

https://build.spring.io/browse/INTSAMPLES-NIGHTLY-2256

The `AggregatorDemoTest` fails sporadically with no second part from
reply.
That might be as a result of the cached consumers in the
`CachingConnectionFactory`, so several `<int-jms:inbound-gateway>`
for the topic using the same connectionFactory essentially end up
using the same consumer sequentially.
And Broker considers them as a single consumer, therefore only one
message is sent.
---
 .../src/main/resources/META-INF/spring/integration/common.xml    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/basic/jms/src/main/resources/META-INF/spring/integration/common.xml b/basic/jms/src/main/resources/META-INF/spring/integration/common.xml
index 05dba2f1..0824969c 100644
--- a/basic/jms/src/main/resources/META-INF/spring/integration/common.xml
+++ b/basic/jms/src/main/resources/META-INF/spring/integration/common.xml
@@ -14,6 +14,7 @@
 			</bean>
 		</property>
 		<property name="sessionCacheSize" value="10"/>
+		<property name="cacheConsumers" value="false"/>
 	</bean>
 
 	<bean id="requestQueue" class="org.apache.activemq.command.ActiveMQQueue">