Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 31442 invoked from network); 13 Apr 2009 15:50:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Apr 2009 15:50:53 -0000 Received: (qmail 7015 invoked by uid 500); 13 Apr 2009 15:50:52 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 6942 invoked by uid 500); 13 Apr 2009 15:50:52 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 6932 invoked by uid 99); 13 Apr 2009 15:50:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2009 15:50:52 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2009 15:50:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A3DF3234C003 for ; Mon, 13 Apr 2009 08:50:31 -0700 (PDT) Message-ID: <804620090.1239637831655.JavaMail.jira@brutus> Date: Mon, 13 Apr 2009 08:50:31 -0700 (PDT) From: "Kyle Anderson (JIRA)" To: dev@activemq.apache.org Subject: [jira] Created: (AMQ-2207) MasterConnector should take a waitForMaster parameter MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org MasterConnector should take a waitForMaster parameter ----------------------------------------------------- Key: AMQ-2207 URL: https://issues.apache.org/activemq/browse/AMQ-2207 Project: ActiveMQ Issue Type: Improvement Components: Connector Affects Versions: 5.2.0 Reporter: Kyle Anderson Master brokers can be configured to wait for slaves, but slaves cannot be configured to wait for their masters to come online for the first time. Slaves simply log an error on startup and assume they are the master. So without this parameter, if the master and slave are started simultaneously it's possible to have a fault-tolerant master/slave setup or two independent masters. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.