[
https://issues.apache.org/jira/browse/AMQCPP-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671364#comment-15671364
]
Michele Bozzaotre commented on AMQCPP-601:
------------------------------------------
Let me report just an additional detail about this issue.
I'm connecting with this URI:
failover:(tcp://BROKER1:61616,tcp://BROKER2:61616)?randomize=false&backup=true
When I perform the connection with both bokers up and running, I see the same
behaviour described before. Otherwise, if BROKER1 is down at first, it
establishes the connection correctly with BROKER2. After starting again
BROKER1, the connection keeps on BROKER2. Then, if I stop BROKER2, it is able
to quickly switch on BROKER1, exactly as I expect with backup feature enabled!
I don't know if this scenario can be useful to find the error. Anyway I would
like to help in the resolution of this issue.
Any idea on where the error could be?
Thanks
> 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
>
> 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.4#6332)
