Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 16 Nov 2017 12:53:00 +0000 (UTC)
From: "Christopher L. Shannon (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13117322.1510244446000.255504.1510836780821@Atlassian.JIRA>
In-Reply-To: <JIRA.13117322.1510244446000@Atlassian.JIRA>
References: <JIRA.13117322.1510244446000@Atlassian.JIRA> <JIRA.13117322.1510244446185@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (AMQ-6858) Fix several durable subscription
 bridge propagation issues
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Nov 2017 12:53:12 -0000


     [ https://issues.apache.org/jira/browse/AMQ-6858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher L. Shannon resolved AMQ-6858.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.15.3

I'm going to close this as resolved.  Everything seems to be working as intended.  I merged the commits back to 5.15.3 as this is just a bunch of bug fixes and not a new feature.

> Fix several durable subscription bridge propagation issues
> ----------------------------------------------------------
>
>                 Key: AMQ-6858
>                 URL: https://issues.apache.org/jira/browse/AMQ-6858
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, networkbridge
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.16.0, 5.15.3
>
>
> While testing bridging together 3 or more brokers I discovered several problems specifically related to durable subscription propagation.  In general durable network subscriptions were not propagating properly when using more than 2 brokers either by not being created at all, not being removed, or even in some cases the same durable was being added twice and causing bridge failures.
> This jira includes the following changes to fix these issues:
> # Currently proxy network subscriptions are not eligible to be conduit.  For topics it doesn't make sense to not use conduit subscriptions so this should be changed.  For queue subscriptions this can sometimes be useful to conduit as well so I added a new flag for this.  Not allowing conduit topic proxy network subs was causing collisions with durables and breaking bridges
> # The durable sync process should only ignore network durable subs for the specific bridge it is syncing, it should still be re-adding subs for other bridges otherwise they will get dropped
> # On demand subscription removal, the tracked demand sub should be checked to see if it's a network demand sub and if it still has remote durable subs attached to it.  If it does they need to be cleaned up and removed
> # Lastly, when creating a demand subscription the consumerId should only be changed if the consumer is for a direct bridge and not a proxy bridge otherwise the demand won't be properly tracked and removed later 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)