[
https://issues.apache.org/jira/browse/AMQ-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139341#comment-17139341
]
Sunil Ainlod commented on AMQ-6098:
-----------------------------------
Is this implemented in any version?
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
