Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 28700 invoked from network); 6 Jun 2008 14:24:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jun 2008 14:24:23 -0000 Received: (qmail 46101 invoked by uid 500); 6 Jun 2008 14:24:26 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 45926 invoked by uid 500); 6 Jun 2008 14:24:26 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 45915 invoked by uid 99); 6 Jun 2008 14:24:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2008 07:24:26 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2008 14:23:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4643A234C132 for ; Fri, 6 Jun 2008 07:24:00 -0700 (PDT) Message-ID: <1552774906.1212762240282.JavaMail.jira@brutus> Date: Fri, 6 Jun 2008 07:24:00 -0700 (PDT) From: "Kai Hudalla (JIRA)" To: dev@activemq.apache.org Subject: [jira] Updated: (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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Hudalla updated AMQ-1779: ----------------------------- Attachment: amq-1779.patch I have changed the connectWork to loop until it finally gets a connection to the broker instead of re-scheduling itself after a failed connection attempt. This way, the monitor on connectWork is kept until the connection succeeds. In order to make this work, the ActiveMQConnectionConsumer needs to use asyncSendPacket() for registering itself with the consumer to avoid a deadlock on the connectWork. The patch also includes David's fix for the prefetchSize calculation in the EndpointWorker. Kai > 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 > 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.