activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Ehm (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3699) Failover transport: support priority urls
Date Tue, 28 Feb 2012 15:37:46 GMT


Felix Ehm commented on AMQ-3699:

Dejan, is this fix already available to use from version fuse-02-02 ?
With this I still receive this exception :
javax.jms.JMSException: Could not create Transport. Reason: java.lang.IllegalArgumentException:
Invalid connect parameters: {priorityBackup=true}
        at org.apache.activemq.util.JMSExceptionSupport.create(
        at org.apache.activemq.ActiveMQConnectionFactory.createTransport(
        at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(
        at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(
        at org.apache.activemq.ActiveMQConnectionFactory.createConnection(
        at JmsConnector.getNewConnection(
        at JmsConnector.getConnection(
        at JmsTest.getConnection(
        at JmsTest.getNewSession(
        at JmsTest.getSession(
        at JmsTest.getDestination(
        at JmsTest.getDestination(
        at NormalConsumer.listen(
        at NormalConsumer.main(
Caused by: java.lang.IllegalArgumentException: Invalid connect parameters: {priorityBackup=true}
        at org.apache.activemq.transport.failover.FailoverTransportFactory.createTransport(
        at org.apache.activemq.transport.failover.FailoverTransportFactory.doConnect(
        at org.apache.activemq.transport.TransportFactory.doConnect(
        at org.apache.activemq.transport.TransportFactory.connect(
        at org.apache.activemq.ActiveMQConnectionFactory.createTransport(
        ... 12 more


I are very much looking forward to have this feature as it solves a critical production problem.
> Failover transport: support priority urls
> -----------------------------------------
>                 Key: AMQ-3699
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message