[
https://issues.apache.org/jira/browse/AMQ-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592488#comment-15592488
]
ASF subversion and git services commented on AMQ-6472:
------------------------------------------------------
Commit 9b6b31ca2f16243ca3ffceac6ab09ac304f71c65 in activemq's branch
refs/heads/activemq-5.14.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=9b6b31c ]
https://issues.apache.org/jira/browse/AMQ-6472
Durable sync over a network bridge will now also sync non-durable
subscriptions proplrly if the consumer belongs to a destination that is
configured to force network durable subscriptions.
(cherry picked from commit d206621a73e4731b00eff49518ea93ba9a4ee3c0)
> Durable sync over a network bridge should sync forced durable subscriptions
> ---------------------------------------------------------------------------
>
> Key: AMQ-6472
> URL: https://issues.apache.org/jira/browse/AMQ-6472
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, networkbridge
> Affects Versions: 5.14.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.15.0, 5.14.2
>
>
> The syncDurableSubs flag on a network bridge will cause durable subscriptions
> to be synced up on connection. However this only applies to real durable
> subscriptions. There's another option on a network bridge added in AMQ-6383
> that allows forcing subscriptions over a bridge to always been durable. We
> should make sure that normal topic subscriptions are synced properly and that
> virtual consumer subscriptions are also synced properly if the the consumers
> are part of a destination that is configured to force durables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
