activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-5146) RedeliveryPolicy exceeded for crashing consumer
Date Tue, 15 Apr 2014 12:23:14 GMT
Gary Tully created AMQ-5146:
-------------------------------

             Summary: RedeliveryPolicy exceeded for crashing consumer
                 Key: AMQ-5146
                 URL: https://issues.apache.org/jira/browse/AMQ-5146
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.9.1
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.10.0


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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message