[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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.2.0
• Component/s: Broker
• Assignee: Robert Davies
• Reporter: James Strachan
• Created: 28/Feb/06 17:47
• Updated: 15/Oct/08 17:08
• Resolved: 02/Sep/08 11:48

Description

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

Issue Links

• is depended upon by: AMQ-1841 Network of pure master/slave synchronization issue