activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3699) Failover transport: support priority urls
Date Mon, 06 Feb 2012 16:27:59 GMT

     [ 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

        

Mime
View raw message