Hi I just upgraded to 5.1 and there seems to be a very weird behavior regarding the message redelivery. Before upgrade to 5.1, I had the Spring 2.5.3 and 5.0 running fine with the following setup. 1. I have a single producer sending and recording 100 persistent messages to a queue. 2. maximumRedeliveries for message is set to -1 3. I use Spring DefaultMessageListenerContainer (sessionTransacted = true) to create a single exclusive consumer on the queue, and session.rollback(); is randomly called to simulate transaction failure. 4. When the queue size reaches 0, I verify that all 100 messages are correctly received and in order.
Everything 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 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. Thoughts? -- View this message in context: http://www.nabble.com/DefaultMessageListenerContainer-and-5.1-tp17135019s2354p17135019.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
