[AMQ-5679] Wildcard Selector is Cached Against Virtual Topic when Browsing the Topic

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 5.9.1
• Component/s: Broker

Environment

Any

• Assignee: Unassigned
• Reporter: Justin Reock
• Created: 19/Mar/15 20:41
• Updated: 26/Mar/15 22:46
• Resolved: 26/Mar/15 22:46

Description

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.

Issue Links

• relates to: AMQ-5672 Add an option to virtual topic selector cache to enforce only a single selector at a given time