[
https://issues.apache.org/jira/browse/AMQ-6209?focusedWorklogId=885590&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-885590
]
ASF GitHub Bot logged work on AMQ-6209:
---------------------------------------
Author: ASF GitHub Bot
Created on: 17/Oct/23 09:33
Start Date: 17/Oct/23 09:33
Worklog Time Spent: 10m
Work Description: jbonofre commented on PR #174:
URL: https://github.com/apache/activemq/pull/174#issuecomment-1766037358
Closing old PRs.
Issue Time Tracking
-------------------
Worklog Id: (was: 885590)
Time Spent: 0.5h (was: 20m)
> Unmatched messages on consumer queues when using SubQueueCacheSelectorPlugin
> in network of brokers
> --------------------------------------------------------------------------------------------------
>
> 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
> Priority: Major
> Attachments: testOuput.tx
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
