Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 15081 invoked from network); 9 Oct 2009 14:03:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Oct 2009 14:03:17 -0000 Received: (qmail 27773 invoked by uid 500); 9 Oct 2009 14:03:16 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 27739 invoked by uid 500); 9 Oct 2009 14:03:16 -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 27729 invoked by uid 99); 9 Oct 2009 14:03:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2009 14:03:16 +0000 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, 09 Oct 2009 14:03:14 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E982F234C1F2 for ; Fri, 9 Oct 2009 07:02:52 -0700 (PDT) Message-ID: <1845095507.1255096972950.JavaMail.jira@brutus> Date: Fri, 9 Oct 2009 07:02:52 -0700 (PDT) From: "Rob Davies (JIRA)" To: dev@activemq.apache.org Subject: [jira] Resolved: (AMQ-2438) Autotomatic client failover supported? In-Reply-To: <1108880609.1254498540244.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-2438. ----------------------------- Resolution: Fixed Fix Version/s: 5.3.0 If you provide one url to the failover transport - the client will continue to try and connect to that url if a connection is lost - e.g. if you only have a single broker, use failover://(tcp://:) - see http://activemq.apache.org/failover-transport-reference.html for configuration parameters. Also - there should be no message loss or duplicate messages - even if just one broker is ever used (providing it does come back online that is ;)) > Autotomatic client failover supported? > -------------------------------------- > > Key: AMQ-2438 > URL: https://issues.apache.org/activemq/browse/AMQ-2438 > Project: ActiveMQ > Issue Type: Improvement > Affects Versions: 5.2.0 > Environment: generic > Reporter: HiSkill > Fix For: 5.3.0 > > > I looked at the ActiveMQ features at http://activemq.apache.org/features-overview.html. I did not see any mention about automatic client failover. Just wonder if ActiveMQ supports automatic client failover to guarantee zero message loss or duplication in event of server failure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.