Hi Poonam,
the JMS Flow is based on ActiveMQ (it relies on advisories for
notifications of endpoints etc. - so is ActiveMQ specific). We will
be adding an example for setting up the configuration. By default
when using JMSFlow it uses the ActiveMQ peer:// transport, that uses
multicast to discover other nodes. The peer:// protocol is reliable,
so handles fail-over automatically.
As JMSFlow uses Queue's internally, it will automatically handle load
balancing across JBIContainers and handle fail-over scenarios like
you've suggested.
cheers,
Rob
On 23 Sep 2005, at 11:07, Poonam wrote:
I agree Rob that using JMS you can specify remote JMS destinations.
But, If I have two JBI container running on two separate machines.
How do I
relate them? Where do I specify in the config file?
Can I do something like: " If one machine goes down then can the
other take
over the failed situation?
-Poonam
----- Original Message -----
From: "Rob Davies" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 23, 2005 4:57 AM
Subject: Re: [servicemix-user] Is ServiceMix distributed??
Hi Julien,
yes ServiceMix does. Currently it supports clustering, but there is a
JMS NMR distribution mechanism (we call them Flows) that will be
available in the next release (due in about a week) - or so.
cheers,
Rob
On 22 Sep 2005, at 22:53, Julien Martin wrote:
Hello,
From what I understand, the JBI spec does not say much about
distributed NMR.
Does ServiceMix provide for a distrubuted NMR?
Thanks in advance.
Julien.
