activemq-dev 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-2753) Allow duplicate topic subscriptions in a network and use dispatch policy to use highest priority subscriptions such that the duplicates are only used for redundancy
Date Thu, 27 May 2010 17:06:52 GMT

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

Gary Tully commented on AMQ-2753:
---------------------------------

r948911, add priority network consumer dispatch policy that will ignore duplicates such that
there can be redundancy in the network with the addition of suppressDuplicateTopicSubscriptions
attribute on a network bridge, think this should do it.

{code}PolicyEntry policy = new PolicyEntry();
policy.setDispatchPolicy(new PriorityNetworkDispatchPolicy());{code}

> Allow duplicate topic subscriptions in a network and use dispatch policy to use highest
priority subscriptions such that the duplicates are only used for redundancy
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2753
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2753
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.3.2
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> duplicate topic subscriptions are suppressed in a cyclic network, https://issues.apache.org/activemq/browse/AMQ-2030
but there is a use case where they can be usefull.
> imagine a usecase where we produce on the one broker and consume on other. These two
brokers have a cyclic network connection between them. So usually the message is going directly
from broker A to broker B, but when that network connector goes down, topic consumer on broker
B stops receiving messages. We want to have a "message rerouting", so that in failure case
messages start flowing A->C->B route, without a need to re-subscribe. 
> With a cyclic network like this, if we allow the duplicate subscriptions we need to choose
among them to suppress duplicates and reduce network load. https://issues.apache.org/activemq/browse/AMQ-2704
added the audit which can help if we don't choose among the duplicates.
> A PriorityNetworkDispatchPolicy can choose to dispatch to the highest priority subscription
in the case of duplicate network consumers so that the messages are suppressed at source.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message