[jira] [Updated] (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:all-tabpanel ] Hadrian Zbarcea updated AMQ-4899: - Fix Version/s: (was: NEEDS_REVIEW) 5.10.0 5.9.1 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: 5.9.1, 5.10.0 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.2#6252)
[jira] [Updated] (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:all-tabpanel ] Kevin Earls updated AMQ-4899: - Attachment: AMQ4899Test.java Hi Ralph. I've attached a unit test that I wrote to try to reproduce this. However, it works correctly for me. Can you take a look and tell me if you were doing something differently? 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 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)
[jira] [Updated] (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:all-tabpanel ] Ralph McNeal updated AMQ-4899: -- Attachment: AMQ4899Test2.java Your unit test had the default VirtualTopic settings configured on the broker and did not have both consumers on the same queue. See attached modifications. 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)
[jira] [Updated] (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:all-tabpanel ] Timothy Bish updated AMQ-4899: -- Fix Version/s: NEEDS_REVIEWED 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 Priority: Minor Fix For: NEEDS_REVIEWED 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)
[jira] [Updated] (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:all-tabpanel ] Timothy Bish updated AMQ-4899: -- Priority: Minor (was: Major) 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 Priority: Minor 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)
