From dev-return-30311-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Mon Feb 6 16:28:23 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E8CC997A for ; Mon, 6 Feb 2012 16:28:23 +0000 (UTC) Received: (qmail 2865 invoked by uid 500); 6 Feb 2012 16:28:23 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 2775 invoked by uid 500); 6 Feb 2012 16:28:22 -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 2767 invoked by uid 99); 6 Feb 2012 16:28:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 16:28:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Feb 2012 16:28:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 27CD8CB286 for ; Mon, 6 Feb 2012 16:27:59 +0000 (UTC) Date: Mon, 6 Feb 2012 16:27:59 +0000 (UTC) From: "Dejan Bosanac (Resolved) (JIRA)" To: dev@activemq.apache.org Message-ID: <23766729.2479.1328545679164.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1876296828.2418.1328545199222.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Resolved] (AMQ-3699) Failover transport: support priority urls MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AMQ-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3699. -------------------------------- Resolution: Fixed Implemented with svn revision 1241061 > Failover transport: support priority urls > ----------------------------------------- > > Key: AMQ-3699 > URL: https://issues.apache.org/jira/browse/AMQ-3699 > Project: ActiveMQ > Issue Type: New Feature > Affects Versions: 5.5.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.6.0 > > > In some use cases it's important to detect that "local" broker is available and force reconnecting to it. > For example if we have url like > {code}failover:(tcp://local:61616,tcp://remote:61616)?priorityBackup=true{code} > should try to backup "local" transport until it's ready and reconnect there when available. > By default only the first url is considered "priority". If you want to further tune what urls are considered prioritized you can use something like > {code}failover:(tcp://local1:61616,tcp://local2:61616,tcp://remote:61616)?priorityBackup=true&priorityURIs=tcp://local1:61616,tcp://local2:61616{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira