You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Tim Bain (JIRA)" <ji...@apache.org> on 2015/12/20 07:51:46 UTC

[jira] [Created] (AMQ-6098) Allow clients to NACK a message in INDIVIDUAL_ACKNOWLEDGE mode

Tim Bain created AMQ-6098:
-----------------------------

             Summary: Allow clients to NACK a message in INDIVIDUAL_ACKNOWLEDGE mode
                 Key: AMQ-6098
                 URL: https://issues.apache.org/jira/browse/AMQ-6098
             Project: ActiveMQ
          Issue Type: Improvement
            Reporter: Tim Bain


Currently, INDIVIDUAL_ACKNOWLEDGE mode allows clients to ack a specific message, but not to nack it individually.  The two options (throwing a RuntimeException and closing the consumer) will nack all unacked messages, which could be problematic if there is never a point where the client can know that there are no messages currently being (successfully) processed.

Although the JMS spec doesn't explicitly require implementors to provide such a method, that's not to say that we can't go above and beyond the minimum functionality required by the spec.  In this case, we should add the ability to nack a specific message, which will result in the client removing the message from its prefetch buffer and the broker performing a broker-side re-delivery (up to the max attempts, after which it will be moved to the DLQ).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)