activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Phillips (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (AMQ-3798) Network connector does not establish connections to a slave broker after master failure
Date Thu, 12 Apr 2012 14:41:17 GMT

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

Aaron Phillips edited comment on AMQ-3798 at 4/12/12 2:39 PM:
--------------------------------------------------------------

I have observed exactly the same problem.  I also have both a test in code and with activemq
installs that demonstrate a broker that is bridged to a M/S pair can forward messages through
the network to a consumer just fine, but once the M/S pair goes into failover with the Slave
being live, the producer attached to the forwarding broker hangs indefinitely when trying
to open a session to produce a message.

This is the architecture in play

(producer) -> [forwarding broker] -> [Master/Slave pair] -> (consumer)

As I mentioned, I have modeled this problem both in code and using 3 activemq installations
(one for each of the brokers), and in both cases, the forwarding broker (with a bridge connection)
fails to push anything to the Slave broker

This has been tested on 5.6-SNAPSHOT (fetched just two days ago) and on 5.5.  Both suffer
the same problem.
The forwarding broker has a networkConnector like so:
<networkConnector name="bridge" uri="masterslave:(tcp://master:61616,tcp://slave:61616)"
/>
                
      was (Author: adphillips):
    I have observed exactly the same problem.  I also have both a test in code and with activemq
installs that demonstrate a broker that is bridged to a M/S pair can forward messages through
the network to a consumer just fine, but once the M/S pair goes into failover with the Slave
being live, the producer attached to the forwarding broker hangs indefinitely when trying
to open a session to produce a message.

This is the architecture in play

(producer) -> [forwarding broker] -> [Master/Slave pair] -> (consumer)

As I mentioned, I have modeled this problem both in code and using 3 activemq installations
(one for each of the brokers), and in both cases, the forwarding broker (with a bridge connection)
fails to push anything to the Slave broker
                  
> Network connector does not establish connections to a slave broker after master failure
> ---------------------------------------------------------------------------------------
>
>                 Key: AMQ-3798
>                 URL: https://issues.apache.org/jira/browse/AMQ-3798
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Hanno Wiegard
>         Attachments: MasterSlaveNetworkTest.java, TestConsumer.java, TestProducer.java,
master.xml, slave.xml
>
>
> We have a broker A which is connected to a master/slave pair (M/S) using a network connector
with a static:failover configuration. A producer P writes to boker A and a consumer C consumes
from brokers M/S. After M fails S becomes active but the no data flows from P to C anymore.
Data seems to be stuck on A. 
> The master/slave pair is a normal ActiveMQ installation (attached config files master.xml
and slave.xml). Broker A is started within a java process which runs in the TestProducer.java
code, TestConsumer.java consumes messages from the master/slave pair.
> Attached testcase shows the same behaviour.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message