[
https://issues.apache.org/activemq/browse/AMQ-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ying updated AMQ-596:
---------------------
Attachment: AMQ1832-596-1820Patch.txt
I was working on issues AMQ-596, AMQ-1832 and AMQ-1820 so that the network of
pure master/slave pair topology can be reliable for use in a production
environment. The common thing of these issues is we want to make sure that
master/slave are always in sync regardless of which one starts first.
Please take a look at the patch I provide. I hope that it can be incorporated
into the source so it will be easy to maintain for us. Please also advise if
there is a better to code to fix these issues. I will like to contribute to fix
these.
NOTE: For AMQ-1820, the fix was found by another user and I simply incorporate
it in this patch. From the testing, without the change in AbstractRegion.java,
1820 exception still happens. That one line change seems a fix
> allow a broker to be configured to start up as a 'Master' and refuse to
> perform any work until the 'Slave' has started
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-596
> URL: https://issues.apache.org/activemq/browse/AMQ-596
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Reporter: James Strachan
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: AMQ1832-596-1820Patch.txt
>
>
> Some folks might not want to start up a system and do work until the slave
> has actually started to avoid the risk of a message being only on one machine.
> So some kinda optional flag on a broker to mark it as being a master on
> startup such that all connections are refused until a slave connects to it
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
