Why should the DefaultMessageListenerContainer not use a CachingConnectionFactory?

I read spring documentation on DefaultMessageListenerContainer

It says: “Note: do not use spring CachingConnectionFactory in combination with dynamic scaling. Ideally, do not use it with the message listener container at all, since it is usually preferable that the listener container itself process the appropriate caching during its life cycle. Also, stop and restarting the listener container will only work with an independent locally cached connection - not a cached one from the outside. "

Can anyone explain why?