[jira] [Commented] (AMQ-6373) Add a command to synchronize durable subscriptions over a network bridge

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-6373:
------------------------------------------------------

Commit e73ab348375db71116624326d29398e0088d7334 in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=e73ab34 ]

https://issues.apache.org/jira/browse/AMQ-6383
https://issues.apache.org/jira/browse/AMQ-6373

Adding a new flag that can be specified on a network bridge to allow
forcing of subscriptions to be durable.  Cleaned up some unit tests.


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