Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 2 Apr 2014 23:43:19 +0000 (UTC)
From: "Hadrian Zbarcea (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12679928.1384860553910.54810.1396482199103@arcas>
In-Reply-To: <JIRA.12679928.1384860553910@arcas>
References: <JIRA.12679928.1384860553910@arcas>
Subject: [jira] [Updated] (AMQ-4897) Race condition in failover transport
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadrian Zbarcea updated AMQ-4897:
---------------------------------

    Fix Version/s: 5.9.1

> Race condition in failover transport
> ------------------------------------
>
>                 Key: AMQ-4897
>                 URL: https://issues.apache.org/jira/browse/AMQ-4897
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.9.1, 5.10.0
>
>
> There's a small chance of the race condition when using priority backup with extremely small reconnect delay (0). In that case, the failover transport will get into inconsistent state. The client will stay connected to the "non-priority" broker, but the priority backup will not be created due to this inconsistency.
> The solution is to synchronise handling of connection failure with the reconnect mutex.


--
This message was sent by Atlassian JIRA
(v6.2#6252)