activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Posta (JIRA)" <>
Subject [jira] [Commented] (AMQ-5679) Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic
Date Fri, 20 Mar 2015 13:55:38 GMT


Christian Posta commented on AMQ-5679:

Yes! i think blacklisting or excluding selectors (specific ones, or even "turn wildcards off")
would be reasonable configuration. 

> Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic
> -------------------------------------------------------------------------
>                 Key: AMQ-5679
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.9.1
>         Environment: Any
>            Reporter: Justin Reock
>            Priority: Minor
> The fix for AMQ-4899 seems to have created an undesired side effect.  Because all consumer
selectors issued against a Virtual Topic are now cached, this means that even the Wildcard
selector used when browsing the Virtual Topic is cached as well.  This effectively nullifies
the selectorAware attribute of the Virtual Topic, as once the browse happens, every message
will be retained in the Topic, regardless of whether they match a desired consumer selector.
> To validate, create a selectorAware Virtual Topic and attach a consumer with a selector
active on the Topic.  Produce some messages which don't match the selector, and note that
they are properly discarded.  Then, browse the Virtual Topic using the web console, and produce
some messages that don't match the selector again.  They will be retained on the Virtual Topic.

This message was sent by Atlassian JIRA

View raw message