[
https://issues.apache.org/jira/browse/AMQ-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284493#comment-15284493
]
Patrik Dudits commented on AMQ-6209:
------------------------------------
I cleaned up the test a bit, however the functionality remains the same until I
will have a hint what might go wrong during restart - it doesn't seem to be
different from other such test cases.
> Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin
> in network of browsers
> ---------------------------------------------------------------------------------------------------
>
> Key: AMQ-6209
> URL: https://issues.apache.org/jira/browse/AMQ-6209
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.2
> Reporter: Patrik Dudits
>
> When using SubQueueSelectorCachePlugin to preserve consumers' selectors in
> network of brokers, the queues start matching all messages after consumers
> failover between brokers.
> The underlying reason is, that {{SubQueueSelectorCacheBroker}} would cache
> selector {{TRUE}} for connected demand subscription, and therefore will
> permanently match all messages even if actual consumer reconnects.
> Additionally, browsing the queue will also cause {{TRUE}} selector to be
> persisted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
