[
https://issues.apache.org/jira/browse/AMQ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james updated AMQ-6456:
-----------------------
Attachment: exclusive_consumer_patch.txt
I've attached exclusive_consumer_patch.txt with changes which seem to fix the
issue for us. according to the docs i could find, the "first" exclusive
consumer is the "chosen" one. i'm assuming that the order returned by the
destination reflects the relevant order (i couldn't find any other way to know
which exclusive consumer is the "chosen" one).
> 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)
