thing was working fine in 5.0, but in 5.1, I noticed that
>>> duplicate
>>> messages were received. However, if I change the cacheLevelName on
>>> the
>>> DefaultMessageListenerContainer from the default CACHE_CONSUMER to
>>> anything else, the te
s message in context:
http://www.nabble.com/DefaultMessageListenerContainer-and-5.1-tp17135019s2354p17136302.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
could you raise a jira for this issue so we can track it ?
cheers,
Rob
http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/
om the default CACHE_CONSUMER to
> anything else, the test then runs fine. However, since I also have
> exponential backoff implemented for redelivery, changing the cache level
> will render the policy useless since the connection & session are
> recreated by the container.
>
&g
, since I also have exponential
backoff implemented for redelivery, changing the cache level will render the
policy useless since the connection & session are recreated by the
container.
Thoughts?
--
View this message in context:
http://www.nabble.com/DefaultMessageListenerContainer-and
