[
https://issues.apache.org/jira/browse/AMQ-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371298#comment-14371298
]
Justin Reock commented on AMQ-5679:
-----------------------------------
It sure looks like it would be, thanks! Apart from adding the cleanup period,
etc, in AMQ-5672, might that work also include being able to explicitly
blacklist certain selectors? The fix for this scenario, in my mind, would be
to have something in place that would allow me to tell ActiveMQ to never cache
a wildcard selector against the destination - but I could see it being useful
for arbitrary selectors as well.
> Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic
> -------------------------------------------------------------------------
>
> Key: AMQ-5679
> URL: https://issues.apache.org/jira/browse/AMQ-5679
> 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
(v6.3.4#6332)
