Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <483467762.1212778804802.JavaMail.jira@brutus>
Date: Fri, 6 Jun 2008 12:00:04 -0700 (PDT)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1779) RA does not reconnect correctly to a
 failed broker
In-Reply-To: <374405526.1212760800364.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Rob Davies resolved AMQ-1779.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Patch applied by SVN revision 664079 and 664082

> RA does not reconnect correctly to a failed broker
> --------------------------------------------------
>
>                 Key: AMQ-1779
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1779
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.0.0, 5.1.0
>            Reporter: Kai Hudalla
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>         Attachments: amq-1779.patch
>
>
> The Resource Adapter does not cleanly reconnect to a failed broker:
> - it uses stale sessions to deliver messages to an Endpoint resulting in messages not being delivered at all anymore after the connection has been re-established
> - the code for connecting/reconnecting to the broker is not synchronized properly leading to race conditions/deadlocks in some situations
> Kai

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.