Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <18225430.post@talk.nabble.com>
Date: Tue, 1 Jul 2008 14:13:16 -0700 (PDT)
From: bwtaylor <bryan_w_taylor@yahoo.com>
To: camel-user@activemq.apache.org
Subject: Camel in Master/Slave ActiveMQ config
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Can somebody explain, or forward me to an explanation of how Camel embedded
in ActiveMQ will behave when used in a master/slave broker configuration. Is
there a way to tell the entire camel context on each broker instance to obey
master/slave status of ActiveMQ?

Specifically when the slave starts up, presumably the camel context and
routes will be built even though the broker is not actively processing
messages. The master will have a comparable camel context, and I'm worried
about interference between the two Camel Context. How do the routes on the
slave know not to try to do their processing? Some routes in these contexts
will reference broker endpoints, but some may do things like hit external
endpoints, which would be bad if this is competing with the comparable
processing on the master.


-- 
View this message in context: http://www.nabble.com/Camel-in-Master-Slave-ActiveMQ-config-tp18225430s22882p18225430.html
Sent from the Camel - Users mailing list archive at Nabble.com.