Christopher L. Shannon created AMQ-6383:
-------------------------------------------
Summary: Add a flag to allow forcing network subscriptions to be
durable
Key: AMQ-6383
URL: https://issues.apache.org/jira/browse/AMQ-6383
Project: ActiveMQ
Issue Type: New Feature
Components: Broker, networkbridge
Affects Versions: 5.13.4
Reporter: Christopher L. Shannon
Assignee: Christopher L. Shannon
When there is a network bridge for two brokers and a topic is included, there
is a conduit subscription created for the topic. This can cause issues if
there is a mixture of durable and non-durable subscriptions.
The issue is that when the conduit subscription gets created, the type of the
subscription across the bridge can be either durable or non-durable depending
on which local subscription gets created first. This is a problem because you
might end up with local durable subs but the network bridge conduit sub is
actually non-durable. This can also cause issues if all of the consumers go
away because then the conduit sub gets destroyed instead of being retained if
it was durable.
To fix this scenario I think there should be an option to force the conduit
subscription to be durable. This could be done on a per topic basis or topic
hierarchy. Something like the following:
{code:xml}
<networkConnector name="broker1" duplex="true"
uri="static:(tcp://10.x.x.x:61616)">
<dynamicallyIncludedDestinations>
<topic physicalName="test.topic?forceDurable=true"/>
</dynamicallyIncludedDestinations>
</networkConne
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
