You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/11 18:03:11 UTC
[jira] [Resolved] (QPID-3542) Java client does not ack non-matching
messages when using client side selectors (CPP Broker)
[ https://issues.apache.org/jira/browse/QPID-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-3542.
------------------------------
Resolution: Fixed
Assignee: Andrew MacBean (was: Keith Wall)
Patch applied.
> Java client does not ack non-matching messages when using client side selectors (CPP Broker)
> --------------------------------------------------------------------------------------------
>
> Key: QPID-3542
> URL: https://issues.apache.org/jira/browse/QPID-3542
> Project: Qpid
> Issue Type: Sub-task
> Components: Java Client
> Affects Versions: 0.13
> Reporter: Andrew MacBean
> Assignee: Andrew MacBean
> Attachments: 0001-QPID-3542-Java-client-does-not-ack-non-matching-mess.patch
>
>
> For topic destinations when client side selectors are in-use, the Java client must ack all messages that do not match the JMS selector. Presently this does not happen and the messages remain un-ack'd on the CPP Broker.
> The defect does not manifest itself on the Java Broker as it uses server side selectors nor the non-0.10 code paths.
> Investigation has shown that the defect is due to a contradiction in the logic with the checkPreConditions method of BasicMessageConsumer_0_10.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org