Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 4 Nov 2015 00:31:27 +0000 (UTC)
From: "Justin Bertram (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12910052.1446569421000.144645.1446597087746@Atlassian.JIRA>
In-Reply-To: <JIRA.12910052.1446569421000@Atlassian.JIRA>
References: <JIRA.12910052.1446569421000@Atlassian.JIRA>
 <JIRA.12910052.1446569421883@arcas>
Subject: [jira] [Resolved] (ARTEMIS-293) Rebalance JCA RA inflow connections
 when cluster topology changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Justin Bertram resolved ARTEMIS-293.
------------------------------------
    Resolution: Fixed

> Rebalance JCA RA inflow connections when cluster topology changes
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-293
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-293
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>    Affects Versions: 1.1.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>             Fix For: 1.1.1
>
>
> The inflow connections for an MDB (or other JCA inflow component) are typically long-lived. This is normally a good thing. However, when MDBs are consuming messages from a remote cluster and the topology of that cluster changes (i.e. a node is added to increase capacity or removed for maintenance) the inflow connections don't react in an efficient way. The RA should detect topology changes and re-balance the inflow connections across the new topology.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)