You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Patrik Dudits (JIRA)" <ji...@apache.org> on 2016/05/11 18:25:12 UTC

[jira] [Updated] (AMQ-6209) Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network of browsers

     [ https://issues.apache.org/jira/browse/AMQ-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrik Dudits updated AMQ-6209:
-------------------------------
    Summary: Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network of browsers  (was: Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network of brosers)

> 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)