> When using the pool the calls to createConnection will create up to max connections before returning > already existing connections, so if you want a durable subscription on a pooled connection type setup you > must limit it to one connection
When I try with maxCOnneciton to "1" and by using same connection factory to be used for all the durable listeners, I get below error on the client side: org.springframework.jms.listener.DefaultMessageListenerContainer#refreshConnect‌​ionUntilSuccessful 875 WARN] - Could not refresh JMS Connection for destination 'topic://.seedTCAStatusPush' - retrying in 5000 ms. Cause: Setting clientID on a used Connection is not allowed ** Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-tp4684381p4684437.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
