You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2014/01/21 20:47:19 UTC

[jira] [Commented] (AMQ-4899) Multiple consumers of the same virtual topic queue cannot have different message selectors

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

Timothy Bish commented on AMQ-4899:
-----------------------------------

Do you have a JUnit test case that can reproduce this?

> Multiple consumers of the same virtual topic queue cannot have different message selectors
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4899
>                 URL: https://issues.apache.org/jira/browse/AMQ-4899
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.x
>            Reporter: Ralph McNeal
>
> If two consumers of the same virtual topic queue have different message selectors, only one selector gets cached via the SubQueueSelectorCacheBroker.java. The problem is when the consumers are offline. Because the cache only caches one selector, the broker will only allow messages that "pass" the cached selector to be put in the queue. All other messages that may be intended for the other consumer will be lost. The fix would allow multiple selectors to be cached per Virtual Topic Consumer queue vs. one.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)