[
https://issues.apache.org/jira/browse/AMQ-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011160#comment-15011160
]
Christopher L. Shannon commented on AMQ-6050:
---------------------------------------------
[~gtully], Mind taking a look at this to make sure the fix looks good? It was
a simple one line fix in DemandForwardingBridgeSupport and I think it's fine.
I included a test case (NetworkDurableRecreationTest) with 4 tests that all
break without this fix, but pass with it. In the meantime, I'm going to let
Jenkins run and see if this change causes other issues.
> Recreated durable after deletion in a network of brokers won't receive
> messages
> -------------------------------------------------------------------------------
>
> Key: AMQ-6050
> URL: https://issues.apache.org/jira/browse/AMQ-6050
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.12.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> When using {{dynamicallyIncludedDestinations}} with a network of brokers, if
> a durable subscription is removed, and then the same one is recreated again,
> it will no longer receive messages from a networked broker.
> The issue is that the networked broker thinks the original subscription
> demand is still there so that when it is re-created, it doesn't re-create the
> demand subscription. This happens in the createDemandSubscription method in
> DurableConduitBridge. The check for addToAlreadyInterestedConsumers is
> returning true even though there is no currently interested consumers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
