[ https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552368#comment-15552368 ]
james commented on AMQ-6456: ---------------------------- if we could confine our exclusive consumers to a single broker, then we would essentially be implementing the exclusive consumer feature on our own. technically, we _could_ do it (non-trivial on our end), but we thought we were getting the feature out of the box with activemq. > Exclusive consumer may stop consuming in broker network > ------------------------------------------------------- > > Key: AMQ-6456 > URL: https://issues.apache.org/jira/browse/AMQ-6456 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.9.1, 5.14.1 > Reporter: james > Priority: Critical > Attachments: exclusive_consumer_patch.txt > > > When exclusive consumers are restarted in a network of brokers, the "chosen" > consumer may shift from one broker to the next. In order for existing > messages to be consumed, they must be forwarded from the broker on which they > currently exist to the broker on which the chosen consumer now resides. > However, the ConditionalNetworkBridgeFilter incorrectly decides that it > should not forward the messages and they end up getting stuck on the old > broker. > We found the issue in 5.9.1, but the relevant code looks unchanged in the > current 5.x release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)