Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Sun, 2 Feb 2014 20:45:06 -0800 (PST)
From: artnaseef <art@artnaseef.com>
To: users@activemq.apache.org
Message-ID: <1391402706736-4677288.post@n4.nabble.com>
In-Reply-To: <1391288745956-4677266.post@n4.nabble.com>
References: <1391288745956-4677266.post@n4.nabble.com>
Subject: Re: Adding/removing brokers from a static broker network
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Sounds like your trying to architect a solution.  If that's the case, there
are lots of ways to slice the problem, depending on the exact needs trying
to be met.  For example, if adding or removing a broker is a once-a-year
action, then manual edits of configuration files may be perfectly
acceptable.  On the other hand, if it will happen daily, then manual edits
will be cumbersome.

There are other considerations for a network-of-brokers, especially scale.

Can you describe what you are trying to accomplish in more detail?


--
View this message in context: http://activemq.2283324.n4.nabble.com/Adding-removing-brokers-from-a-static-broker-network-tp4677266p4677288.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.