activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrik Dudits (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6209) Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin in network of browsers
Date Tue, 17 May 2016 16:21:12 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286935#comment-15286935
] 

Patrik Dudits commented on AMQ-6209:
------------------------------------

That is surprising, as I was starting with a failing test. I'll have to check in different
environments again. It may take few days to get back to this.

> 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
>         Attachments: testOuput.tx
>
>
> 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)

Mime
View raw message