[
https://issues.apache.org/activemq/browse/AMQ-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46485#action_46485
]
Gary Tully commented on AMQ-596:
--------------------------------
BrokerService has a new attribute: waitForSlave
from the svn log, see:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/resources/activemq.xsd?p2=%2Factivemq%2Ftrunk%2Factivemq-core%2Fsrc%2Fmain%2Fresources%2Factivemq.xsd&p1=%2Factivemq%2Ftrunk%2Factivemq-core%2Fsrc%2Fmain%2Fresources%2Factivemq.xsd&r1=691206&r2=691205&view=diff&pathrev=691206
> 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.
