activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Earls (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-4899) Multiple consumers of the same virtual topic queue cannot have different message selectors
Date Fri, 07 Feb 2014 08:45:19 GMT

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

Kevin Earls resolved AMQ-4899.
------------------------------

    Resolution: Fixed

Updated SubQueueSelectorCacheBroker and SelectorAwareVirtualTopicInterceptor to handle more
than one selector per topic. 

Ralph, thanks for the updated test.


> 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
>            Assignee: Kevin Earls
>            Priority: Minor
>             Fix For: NEEDS_REVIEWED
>
>         Attachments: AMQ4899Test.java, AMQ4899Test2.java
>
>
> 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)

Mime
View raw message