activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6456) Exclusive consumer may stop consuming in broker network
Date Thu, 06 Oct 2016 14:20:21 GMT

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

Gary Tully commented on AMQ-6456:
---------------------------------

yes. and by stop working - messages will get isolated on a broker because it won't forward
because the forwarding sub is not the local exclusive consumer.
And you have the additional problem of "forwarding back" b/c there will be some consumers
present and active.

If your competing exclusive consumers can be confined to a single broker at a time, it will
work.

> 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)

Mime
View raw message