[
https://issues.apache.org/jira/browse/QPID-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reopened QPID-3542:
------------------------------
Reopening as behaviour in the following scenario is not correct: In the case
where client side filtering is in use, and the message has not been
pre-acquired, 0-10 requires us to mark the command as completed. This is not
happening. This is not a regression as this was not happening prior to this
commit.
Secondly the principle behind the new system
TopicSessionTest#testNonMatchingMessagesHandledCorrectlly is flawed. It relies
on changing the selector to demonstrate that the message remained on the
Broker, but changing the selector should "[be] equivalent to unsubscribing
(deleting) the old one and creating a new one" (JMS Javadoc :
http://download.oracle.com/javaee/6/api/javax/jms/Session.html#createDurableSubscriber(javax.jms.Topic,%20java.lang.String,%20java.lang.String,%20boolean)).
> 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:[email protected]
