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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on AMQ-6209:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Mar/21 08:39
            Start Date: 08/Mar/21 08:39
    Worklog Time Spent: 10m 
      Work Description: lucastetreault commented on pull request #174:
URL: https://github.com/apache/activemq/pull/174#issuecomment-792580665


   Can one of the admins verify this patch?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 562212)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>            Priority: Major
>         Attachments: testOuput.tx
>
>          Time Spent: 10m
>  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.3.4#803005)