[
https://issues.apache.org/jira/browse/AMQ-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-4164.
-----------------------------
Resolution: Won't Fix
This is no longer an issue as we don't support pure master / slave any longer.
> In network of master slave brokers, if both masters down, slaves incorrectly
> create treat each other as slaves
> --------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4164
> URL: https://issues.apache.org/jira/browse/AMQ-4164
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.7.0
> Reporter: Martin Serrano
> Attachments: amq-4164.patch
>
>
> When running a test with a network of master/slave brokers, I have both
> masters go down. In this case, the slaves are started and their respective
> network connections are started. The logic in
> {{TransportConnection.processBrokerInfo(BrokerInfo info)}}, checks if the
> info represents a slave broker and starts a MasterBroker filter if so.
> However this logic is faulty if the info for the slave broker is arriving via
> a network connection.
> As a result a slave tries to connect a networked broker as a slave. This
> results in incorrect behavior, errors, and can cause the system to lockup
> during shutdown (due to hanging ResponseCorrelation).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
