[
https://issues.apache.org/jira/browse/AMQ-7312?focusedWorklogId=320217&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-320217
]
ASF GitHub Bot logged work on AMQ-7312:
---------------------------------------
Author: ASF GitHub Bot
Created on: 29/Sep/19 14:21
Start Date: 29/Sep/19 14:21
Worklog Time Spent: 10m
Work Description: couclock commented on pull request #395: AMQ-7312
virtualSelectorCacheBrokerPlugin addConsumer issue
URL: https://github.com/apache/activemq/pull/395
See details on https://issues.apache.org/jira/browse/AMQ-7312
On "browse" action in AMQ console, a consumer is added on related queue.
When virtualSelectorCacheBrokerPlugin is activated, "addConsumer" method add
a 'TRUE' selector on that queue that disable previous cached selector.
Could you please merge that PR on next release ?
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 320217)
Remaining Estimate: 0h
Time Spent: 10m
> virtualSelectorCacheBrokerPlugin fails on "browse" action
> ---------------------------------------------------------
>
> Key: AMQ-7312
> URL: https://issues.apache.org/jira/browse/AMQ-7312
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.10
> Reporter: Dany LECOQ
> Priority: Critical
> Fix For: 5.15.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have a VirtualTopic "VirtualTopic.multi_dest" and 2 consumers :
> * Consumer.alpha.VirtualTopic.multi_dest
> * Consumer.beta.VirtualTopic.multi_dest
> Message producer send messages on that vTopic with various "tenant" header
> value.
> Each consumer use a selector to receive only desired data :
> * tenant='alpha' for Consumer.alpha.VirtualTopic.multi_dest
> * tenant='beta' for Consumer.alpha.VirtualTopic.multi_dest
> To avoid to get many pending message on each consumer queue, we activated
> selectorAware="true" in broker settings.
> To avoid to lose message on temporary consumer deconnection, we activated
> virtualSelectorCacheBrokerPlugin plugin.
> Steps to reproduce bug :
> * launch message producer and both message consumers alpha and beta
> * stop alpha consumer
> * notice on console pending messages on alpha queue increase
> * if we restart alpha consumer, all pending messages are consumed => ok,
> only messages matching selector were in queue
> * restop alpha consumer
> * go on console and click on "Browse" link for alpha consumer queue
> * restart alpha consumer => it will consume pending messages matching
> selector
> * notice there are other waiting messages that do not match selector, so the
> consumer queue is fastly full of useless messages => ko
> * even after broker restart, the alpha consumer queue continues to receive
> message that do not match selectors => ko
>
> After code analysis, I notice "Browse" action create a new consumer on queue.
> In virtualSelectorCacheBrokerPlugin, the addConsumer method update
> "subSelectorCache" variable with 'TRUE' selector.
>
> A pull request will be submitted to fix that issue, could you merge it for
> the next patch 5.15.11 ?
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
