activemq-dev mailing list archives

[jira] Updated: (AMQ-596) allow a broker to be configured to start up as a 'Master' and refuse to perform any work until the 'Slave' has started

Date

Thu, 10 Apr 2008 11:51:44 GMT

[ https://issues.apache.org/activemq/browse/AMQ-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies updated AMQ-596:
---------------------------
Fix Version/s: 5.2.0
(was: 5.1.0)
> 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
>
>
> 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.