[
https://issues.apache.org/jira/browse/QPID-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-792:
-----------------------------
Fix Version/s: (was: M4)
AFAICT Now work has been done on this JIRA (AMQQueueBrowser still creates a
consumer and closes it to validate selector validity) and therefore it will
not be part of M4. Descoping...
> Need to revise QueueBrowser implementation strategy
> ---------------------------------------------------
>
> Key: QPID-792
> URL: https://issues.apache.org/jira/browse/QPID-792
> Project: Qpid
> Issue Type: Improvement
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
>
> While debuggin and issue I noticed the following behaviour in the
> AMQQueueBrowser class.
> 1) When we create a queue browser we do a subscribe immediately
> followed by a cancel. (And then we subscribe again when we enumerate).
> The rationale for doing so it to verify the selector is valid. This is
> very confusing for customers who look at the log and it is not appropriate
> IMHO.
> Currently we use client side selectors, so it is easy validate this. The
> above step is completely unnecessary.
> If we are to use server side selectors the right way to do is
> a)Send a subscribe with the selector
> b)Give message credits only when you call the enumerate method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
