Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sat, 30 Jul 2016 07:19:20 +0000 (UTC)
From: "Jawad Bokhari (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12993390.1469745480000.176539.1469863160468@Atlassian.JIRA>
In-Reply-To: <JIRA.12993390.1469745480000@Atlassian.JIRA>
References: <JIRA.12993390.1469745480000@Atlassian.JIRA> <JIRA.12993390.1469745480793@arcas>
Subject: [jira] [Updated] (AMQCPP-601) PriorityBackup isn't working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 30 Jul 2016 07:19:22 -0000


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

Jawad Bokhari updated AMQCPP-601:
---------------------------------
    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 remote
While connected to remote, if local comes back up, we then reconnect to local.
I have had success with testing it on the java apps by simply adding priorityBackup to my uri options i.e. failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true

However stuff isn't going as smoothly on the CPP side.

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 seems to break 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

Is there anything I am missing here? Extra uri options that I should have included?
http://stackoverflow.com/questions/27114156/issues-with-activemq-3-8-3-cpp-prioritybackup-not-working

I'm still facing the same issue with version 3.9.3. 
I'm using Visual Studio 2008 toolset (V90) for my client application. 


  was:
The priroity backup feature isn't working for me and am having the same issue as explained by another user on StackOverflow 

http://stackoverflow.com/questions/27114156/issues-with-activemq-3-8-3-cpp-prioritybackup-not-working

I'm still facing the same issue with version 3.9.3. 
I'm using Visual Studio 2008 toolset (V90) for my client application. 


> 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 remote
> While connected to remote, if local comes back up, we then reconnect to local.
> I have had success with testing it on the java apps by simply adding priorityBackup to my uri options i.e. failover:(tcp://local:61616,tcp://remote:61616)?randomize=false&priorityBackup=true
> However stuff isn't going as smoothly on the CPP side.
> 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 seems to break 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
> Is there anything I am missing here? Extra uri options that I should have included?
> http://stackoverflow.com/questions/27114156/issues-with-activemq-3-8-3-cpp-prioritybackup-not-working
> I'm still facing the same issue with version 3.9.3. 
> I'm using Visual Studio 2008 toolset (V90) for my client application. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)