activemq-issues mailing list archives

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

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

Timothy Bish updated AMQ-6209:
------------------------------
    Attachment: testOuput.tx

Test fails using the latest patch, I don't have time to debug it so here is the console output
from the test.  

PS. You should squash the commits in you PR otherwise we won't be able to apply it when the
time comes.  

> 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