[ https://issues.apache.org/jira/browse/AMQNET-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-489. --------------------------------- Resolution: Fixed Fixed on trunk and the 1.6.x branch. > Port fixes from AMQ-5146 to NMS.ActiveMQ > ---------------------------------------- > > Key: AMQNET-489 > URL: https://issues.apache.org/jira/browse/AMQNET-489 > Project: ActiveMQ .Net > Issue Type: Bug > Components: ActiveMQ > Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.6.3 > Reporter: Timothy Bish > Assignee: Timothy Bish > Fix For: 1.6.4, 1.7.0 > > > From the AMQ-5146 issue: > {quote} > A consumer with a transacted session that dies after receive or in onMessage > (due to some of the message content for example), but before the a > transaction can complete will continue to receive the message. > The connection will die, the transaction will rollback, the broker will > increment the redeliveryCounter and redispatch the message. > However the redeliveryPolicy, which is only checked on rollback (client side) > will never kick in. > the result is infinite redelivery with an ever incrementing redeliveryCounter. > It is a reasonable expectation that this message would eventually find its > way into the dlq. > The broker redelivery plugin does not help because it is triggered by the > client side poison ack. > Either the broker redelivery plugin can get involved before dispatch, or a > client can do a predispatch check. > {quote} > We should look at porting the fixes done there over to NMS.ActiveMQ -- This message was sent by Atlassian JIRA (v6.2#6252)