You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Justin Reock (JIRA)" <ji...@apache.org> on 2015/03/19 21:42:38 UTC
[jira] [Created] (AMQ-5679) Wildcard Selector is Cached Against
Virtual Topic when Browsing the Topic
Justin Reock created AMQ-5679:
---------------------------------
Summary: 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.
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)