[jira] [Resolved] (AMQCPP-601) PriorityBackup isn't working

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQCPP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQCPP-601.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.9.4

Added several fixes that allow for a bit better behavior of the FailoverTransport when priorityBackup is enabled.  

> PriorityBackup isn't working
> ----------------------------
>
>                 Key: AMQCPP-601
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-601
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.7.0, 3.9.3
>         Environment: MSVC (Toolset v90), 
>            Reporter: Jawad Bokhari
>            Assignee: Timothy Bish
>             Fix For: 3.9.4
>
>
> I am trying to take advantage of the ActiveMQ priority backup feature.
> I'm running 2 brokers on 2 different sites (machines). Each site has 2 AMQ clients, one of which is a Java client and the other one is a C++ client.
> Both brokers are linked as network of brokers in duplex mode. 
> I want the following behavior for my apps.
> * Always connect to local broker on startup
> * If local broker goes down, connect to the remote
> * {color:red} While connected to remote, if local comes back up, we then reconnect to local. {color}
> This works on my java app by simply adding priorityBackup to my URI options 
> ??failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true??
> However, the part highlighted in {color:red}red{color} doesn't work for CPP client.
> The following works fine on the CPP apps (with basic working failover functionality - aka jumping to remote when local goes down )
> ??failover:(tcp://local:61616,tcp://remote:61616)?randomize=false??
> But updating the uri options with priorityBackup even breaks failover functionality completely (my apps never failover to the remote broker, they just stay in some kind of broker-less/limbo state when their local broker goes down) 
> ??failover:(tcp://local:61616,tcp://remote:61616)?randomize=false{color:red}&priorityBackup=true{color}??
> I tried this with 3.9.3 without success. Then, I tried with the version 3.7.0 when this feature *priorityBackup* was first introduced but without luck.
> ActiveMQ broker versions: *5.9.0*, *5.13.2*
> I'm using Visual Studio 2008 toolset (V90) for my client application. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)