Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.7.0, 3.9.3
-
None
-
None
-
MSVC (Toolset v90),
Description
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
- While connected to remote, if local comes back up, we then reconnect to local.
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 red 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&priorityBackup=true
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.