title: Why DefaultMessageListenerContainer should not use CachingConnectionFactory?
body: <p>I was reading spring documentation on <a href="http://docs.spring.io/spring/docs/3.2.7.RELEASE/javadoc-api/org/springframework/jms/listener/DefaultMessageListenerContainer.html" rel="noreferrer">DefaultMessageListenerContainer</a></p>
  
  <p>It says "Note: Don't use Spring's CachingConnectionFactory in combination with dynamic scaling. Ideally, don't use it with a message listener container at all, since it is generally preferable to let the listener container itself handle appropriate caching within its lifecycle. Also, stopping and restarting a listener container will only work with an independent, locally cached Connection - not with an externally cached one."  </p>
  
  <p>Could anybody explain why? </p>