[jira] Reopened: (QPID-545) Using a private queue with selector will result in non matching messages being left on the broker queue as they will not be consumed.

["Martin Ritchie (JIRA)" <qp...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie reopened QPID-545:
---------------------------------

      Assignee:     (was: Martin Ritchie)

Sorry mis-read this issue.

This should be resolved now as we have the ability to apply selectors at the exchange level. 

However this work is not complete.
See: https://issues.apache.org/jira/browse/QPID-1275
for an outstanding issue about selector changes.

Also this needs to be tested on non durable topic subscriptions AND durable/non-durable private queues.

> Using a private queue with selector will result in non matching messages being left on the broker queue as they will not be consumed.
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-545
>                 URL: https://issues.apache.org/jira/browse/QPID-545
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M2
>            Reporter: Martin Ritchie
>             Fix For: M4
>
>
> Because the decision to route a message to a queue is based solely on how the routing information is processed by the exchange private queues that are the messages are routed to may result in a memory leak if that consumer utilises a selector. 
> The selectors are filters applied to the consumption from a queue, however, in a private queue scenario, only one consumer will exist on the queue. This means that any messages that do not match the selector will remain on the queue indefinitely.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.