From dev-return-9506-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Thu Feb 07 05:53:05 2008 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 78500 invoked from network); 7 Feb 2008 05:53:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 05:53:05 -0000 Received: (qmail 35848 invoked by uid 500); 7 Feb 2008 05:52:57 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 35814 invoked by uid 500); 7 Feb 2008 05:52:57 -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 35805 invoked by uid 99); 7 Feb 2008 05:52:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Feb 2008 21:52:57 -0800 X-ASF-Spam-Status: No, hits=-99.8 required=10.0 tests=ALL_TRUSTED,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 05:52:28 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7E1E3714071 for ; Wed, 6 Feb 2008 21:52:35 -0800 (PST) Message-ID: <10105444.1202363555512.JavaMail.jira@brutus> Date: Wed, 6 Feb 2008 21:52:35 -0800 (PST) From: "Jason Rosenberg (JIRA)" To: dev@activemq.apache.org Subject: [jira] Updated: (AMQ-1575) FailoverTransport with MaxReconnectAttempts set does not recover quickly, when used with ConnectionPooling.... In-Reply-To: <7643714.1201991316585.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rosenberg updated AMQ-1575: --------------------------------- Attachment: FailoverTransport.java ConnectionPool.java I've included a patch built against a recent 5.1-SNAPSHOT source (svn rev 618082) The file FailoverTransport.java, includes fixes for 4 issues, including hbuch's fix for this issue. The other issues that this patch includes fixes for are: AMQ-1116 AMQ-1575 AMQ-1577 AMQ-1581 The file ConnectionPool.java is also needed for the fix for AMQ-1581 I've added comments in the code that clearly indicate which sections apply to which issue, so you can easily take edit to include only the fixes you want specifically. Jason > FailoverTransport with MaxReconnectAttempts set does not recover quickly, when used with ConnectionPooling.... > -------------------------------------------------------------------------------------------------------------- > > Key: AMQ-1575 > URL: https://issues.apache.org/activemq/browse/AMQ-1575 > Project: ActiveMQ > Issue Type: Bug > Components: Transport > Affects Versions: 5.0.0 > Environment: 5.1-SNAPSHOT > Reporter: Jason Rosenberg > Attachments: ConnectionPool.java, FailoverTransport.java > > > This entry from the users forum describes the issue (and it includes a reproducible test-case)...See the entry from me dated Dec 06, 2007..... > http://www.nabble.com/Timeout-and-Failover-on-a-queue-to13292887s2354.html#a14215834 > I've confirmed that the issue happens with the latest 5.1-SNAPSHOT version, and happens with either jencks AMQPool, or the built-in activeMQ PooledConnections. The problem does not happen if no connection pooling is used. > Basically, it appears that the FailoverTransport is not properly communicating with the TransportListener when brokers return to service. > Another user ('hbuch) has created a patch, implemented for 4.1.1, which seems to solve the problem, which is also referred to in that same thread referred to above....See entry from 'hbuch' dated Dec 05, 2007.....I've verified that that fix seems to work (tested only under 4.1.1 so far).... > Anyway, it seems that this fix should be straightforward to fold back into the source code for 5.1.... > Please take a look. > Thanks, > Jason -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.