activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-6373) Add a command to synchronize durable subscriptions over a network bridge
Date Mon, 01 Aug 2016 16:29:20 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher L. Shannon resolved AMQ-6373.
-----------------------------------------
    Resolution: Fixed

I'm resolving this for now as we are about to release 5.14.0.  If issues arise they can be
fixed in patch releases.  The behavior is off by default so this should be fine.

> Add a command to synchronize durable subscriptions over a network bridge
> ------------------------------------------------------------------------
>
>                 Key: AMQ-6373
>                 URL: https://issues.apache.org/jira/browse/AMQ-6373
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, networkbridge
>    Affects Versions: 5.13.4
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.14.0
>
>
> When dynamicallyIncludedDestinations are used for a NetworkConnector durable subscriptions
are tracked (added/removed) in the connector.  This allows the broker to create network subscriptions
automatically on a remote broker to match the demand that is created and then to destroy the
network subscriptions when no longer needed.
> The problem with this is that if the bridge is restarted or if the brokers are restarted,
the information about the durable subscriptions is lost.  For example, if the bridge is stopped
and a local durable subscription is added, this new durable will not be added to the remote
conduit network conduit subscription on reconnect.  Or, if a local durable subscription is
removed while the bridge is offline, on reconnect the remote durable sub will not be cleaned
up even if there are no more matching durables.
> To fix this we need to add a new OpenWire command to support the syncing of durable subscriptions
when a bridge is restarted.  The goal of this command is to re-add missing subscriptions and
to clean up no longer needed subscriptions on reconnect.
> Note that this new sync option will only apply when dynamicOnly is false and conduitSubscriptions
is true.  (both of these are enabled by default)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message