[jira] [Commented] (AMQ-2743) Pure master/slave configuration will not failover to slave when master fails

["Scott Emmons (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017147#comment-13017147 ] 

Scott Emmons commented on AMQ-2743:
-----------------------------------

We have seen this same thing. Everything was fine in 5.3.0, but unable to failover to slave in 5.4.2. This is a serious issue - we cannot rollback to 5.3.0 due to other bugs, fixed in later versions - and we can not deploy a fault-tolerant configuration on a newer version, because of this bug.

> Pure master/slave configuration will not failover to slave when master fails 
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2743
>                 URL: https://issues.apache.org/jira/browse/AMQ-2743
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.3.1
>            Reporter: Bruce Snyder
>             Fix For: 5.6.0
>
>         Attachments: activemq-brokerA.xml, activemq-brokerB-master.xml, activemq-brokerB-slave.xml
>
>
> When using a pure/master slave configuration in ActiveMQ 5.3.1 and the master is killed, the failover to the slave never takes place. 
> Below is a description of the topology being used: 
> * The producer sends messages to brokerA 
> * BrokerA has a uni-directional network connection using the failover transport to brokerB-master and brokerB-slave 
> * BrokerB-master and brokerB-slave each have a uni-directional network connection using failover to brokerA 
> * The consumer uses a failover connection to brokerB-master and brokerB-slave 
> Below are the steps to reproduce the problem: 
> # In terminal one, start up brokerA 
> # In terminal two, start up brokerB-master 
> # In terminal three, start up brokerB-slave 
> # In terminal four, start up the consumer that connects to brokerB-master and brokerB-slave  
> # In terminal five, startup the producer that connects to brokerA to send messages 
> # In terminal two, kill brokerB-master 
> # Notice that the producer will continue sending messages until producer flow control kicks in and blocks the send operation, but brokerB-slave never takes over 
> I copied the same exact configuration files over to instances of ActiveMQ 5.3.0 and it works without a problem. There must be something in ActiveMQ 5.3.1 that is causing this issue. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (AMQ-2743) Pure master/slave configuration will not failover to slave when master fails

[jaker <ja...@yahoo.com>]

Hi - 

Please walk me through compiling activeMQ-CPP package.  I downloaded the
following packages and unpacked them into different sub-directories 

main_idr: 
   activeMQ-cpp.3.2.5 
   apr-1.4.2 
   apr-util.1.3.10 
   cppunit.1.12.1 
   libtool-2.4 
   openssl-1.0.0d 

when i "configure" my activeMQ-cpp.3.2.5 package:      ./configure
--with-apr=/usr/local/share/apr 
it doesn't see the apr package. 

configure.ac 
    AC_PREREQ(2.61) <--- it complains about this, but I have 2.68 installed

when I commented AC_PREREQ(2.61) out  and do the following:

./autogen.sh
aclocal
./configure --with-apr=/usr/local/apr

it says "configure: error: invalid apr version found..."

but I installed apr-1.4.2 which is located here [--with-apr=/usr/local/apr]

Please help! 


--
View this message in context: http://activemq.2283324.n4.nabble.com/jira-Commented-AMQ-2743-Pure-master-slave-configuration-will-not-failover-to-slave-when-master-fails-tp3434579p3434673.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.