You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/01/17 18:41:00 UTC
[jira] [Updated] (QPIDJMS-357) add support for acknowledging
individual messages
[ https://issues.apache.org/jira/browse/QPIDJMS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPIDJMS-357:
-----------------------------------
Description:
The "client acknowledgement" session acknowledgement mode allows for messages to be received by the application and for an explicit acknowledgedment step to then be perfomed later after processing through calling Message#acknowledge(). Confusingly however, this does not acknowledge the specific message it is called on but rather every message received on the same Session as the message since the prior such call. Although this is clearly documented in the API docs, many users are confused by this behaviour and understandably expect that calling message#acknowledge() would only affect that specific message. Several implementations provide a different session ack mode value to instead configure sessions for this expected 'individual acknowledgement' behaviour, such that only the message upon which acknowledge() is called is affected, and this was also under discussion for inclusion in JMS 2.1. We should provide this useful functionality.
The integer session acknowledgement mode value used is 101.
was:The "client acknowledgement" session acknowledgement mode allows for messages to be received by the application and for an explicit acknowledgedment step to then be perfomed later after processing through calling Message#acknowledge(). Confusingly however, this does not acknowledge the specific message it is called on but rather every message received on the same Session as the message since the prior such call. Although this is clearly documented in the API docs, many users are confused by this behaviour and understandably expect that calling message#acknowledge() would only affect that specific message. Several implementations provide a different session ack mode value to instead configure sessions for this expected 'individual acknowledgement' behaviour, such that only the message upon which acknowledge() is called is affected, and this was also under discussion for inclusion in JMS 2.1. We should provide this useful functionality.
> add support for acknowledging individual messages
> -------------------------------------------------
>
> Key: QPIDJMS-357
> URL: https://issues.apache.org/jira/browse/QPIDJMS-357
> Project: Qpid JMS
> Issue Type: New Feature
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.29.0
>
>
> The "client acknowledgement" session acknowledgement mode allows for messages to be received by the application and for an explicit acknowledgedment step to then be perfomed later after processing through calling Message#acknowledge(). Confusingly however, this does not acknowledge the specific message it is called on but rather every message received on the same Session as the message since the prior such call. Although this is clearly documented in the API docs, many users are confused by this behaviour and understandably expect that calling message#acknowledge() would only affect that specific message. Several implementations provide a different session ack mode value to instead configure sessions for this expected 'individual acknowledgement' behaviour, such that only the message upon which acknowledge() is called is affected, and this was also under discussion for inclusion in JMS 2.1. We should provide this useful functionality.
> The integer session acknowledgement mode value used is 101.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org