Hi Vikas,
what you are describing is the behavior of a message queue - which we
do support in the JCAFlow and JMSFlow - we call the mechanism for
internal of MessageExchanges within ServiceMix a flow btw - please
see: http://www.servicemix.org/Clustering.
The JCA Flow has the same behavior as the JMS Flow, except it will
enlist the JMS operations in the current running transaction (if
you're using transactions whilst invoking services).
There is an other head above the in-memory flow types (straight
through and seda) in that messages are potentially routed over the
network (depending on the configuration you use).
cheers,
Rob
On 23 Nov 2005, at 06:06, vikas kumar wrote:
Hi everyone,
Am new to this list but have been playing around with some ESBs...
I am looking at the following usecases:
1) I have 2 services called s1,s2. They provide the same services to
the consumer.
*s1 is down between date1 and date2
*s2 is down between date3 and date4.
So i hope to set a configuration that says the incoming request
addressed to
anyone of them that:
* between date1 and date2 - goto s2
* between date3 and date4 - goto s1.
2) I have 'n' number of services S1,S2,...Sn. They all provide the
same service.
I want to configure seamless failover.
i.e. if a request addresed to anyone of the 'n' services (say Si
)comes in, I
should start trying from Si to Sn until one of them succeeds or I
reach the end
without any result.
What are the options in ServiceMix that I can use? Which one has the
least overhead?
All help will be appreciated...
~ Thanks.
Vikas.
