If a message enters a redelivery cycle of e.g. 10 maximum redelivery attempts, and the session is closed halfway through it (e.g. after consuming attempt 5), the next time the session is established and the message is consumed, it will have RedeliveryCount=2 rather than 6. As a result, the message will end up being materially redelivered 14 times, thus exceeding the configured maximum.
With the current set up, where it's the consumer-side AMQ logic who is in charge of tallying up the redelivery attempts and sending back the Poison ACK, it seems that there is a missing command when the session is being closed gracefully from consumer -> broker informing of the redelivery counters of messages in redelivery process.
If the session was being closed suddenly, I suppose to some extent it would be okay to miscount the redeliveries, since there was no chance to execute a closure process for the client to update the broker accordingly.
This is also a case for AMQ to support broker-controlled redeliveries (see
Unit test reproducing the problem is attached.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|55d 3h 8m||1||Timothy Bish||14/May/12 22:33|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Duplicate [ 3 ]|
|Field||Original Value||New Value|
|Affects Version/s||5.5.1 [ 12318549 ]|
|Component/s||Broker [ 12313892 ]|
|Component/s||JMS client [ 12313896 ]|