[
https://issues.apache.org/activemq/browse/AMQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ying updated AMQ-1832:
----------------------
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.
> Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master
> ----------------------------------------------------------------------------
>
> Key: AMQ-1832
> URL: https://issues.apache.org/activemq/browse/AMQ-1832
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: ying
> Attachments: AMQ1832-596-1820Patch.txt
>
>
> It is related to AMQ-596 in terms that it is desirable that master and slave
> are in synch and when both are down, failover can direct the job to other
> pair of master/slave. So pure master/slave can be used for replication while
> a network of pair (master/slave) will provide a HA service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
