You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/11/18 16:08:11 UTC
[jira] [Commented] (AMQ-6050) Recreated durable after deletion in a
network of brokers won't receive messages
[ https://issues.apache.org/jira/browse/AMQ-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011154#comment-15011154 ]
ASF subversion and git services commented on AMQ-6050:
------------------------------------------------------
Commit 09054fc4a85bcdef9e19e589be368d0e9cf0de41 in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=09054fc ]
https://issues.apache.org/jira/browse/AMQ-6050
Clearing the subscription from the local map in
DemandForwardingBridgeSupport to make sure that demand can be properly
recreated again.
> 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
>
> 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)