You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Carlo Camerino <cm...@gmail.com> on 2009/06/15 00:21:40 UTC
Question On Dynamic Integration Pattern
Hi There,
I have a situation in which I need to connect to two different hosts. I need
to be able to switch at runtime to a different host when one host goes down.
What enterprise integration pattern should I use here? I don't know if I
should use Dynamic Routing Or Load Balancing for this one.
The message could only go to one place at a time. As long as the first one
is up then I would have to go to it. But when it goes down, my application
automatically needs to fall back to the other host system.
In what way can I do this via Apache Camel .
Thanks!!!
Carlo
Re: Question On Dynamic Integration Pattern
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
And maybe 1 month ago there was some similar questions regarding load
balancer in Camel 1.x.
You can use nabble to search the camel user forum to find this topic.
On Mon, Jun 15, 2009 at 6:22 AM, Claus Ibsen<cl...@gmail.com> wrote:
> On Mon, Jun 15, 2009 at 12:28 AM, Carlo Camerino<cm...@gmail.com> wrote:
>> It seems that what I was looking for is present in Camel 2.0 which is
>> the failover feature. I have a question though,
>> Can I support failover and at the same time make it round robin? If
>> one node is not functioning then I will no longer use that node.
> Hi
>
> There is a ticket in JIRA about ideas for improvments to the failover
> load balancer.
> We have thoughts of master/slave and having pluggable/selective
> strategies for determine which slave to select etc.
>
> So we are looking for use-cases and descriptions what you need. Please
> feel free to add to this ticket.
> https://issues.apache.org/activemq/browse/CAMEL-1471
>
> But remember you can always extend or write your own logic as a Processor.
> MyOwnLoadBalancer lb = new MyOwnLoadBalancer()
> lb.addMaster("xxxx");
> lb.addSlave("yyyy");
> lb.addSlave("zzz");
> lb.setSelection(RoundRobin);
>
> And use .process(lb) in your route.
>
>
>
>
>>
>> Thanks
>>
>> On Mon, Jun 15, 2009 at 6:21 AM, Carlo Camerino <cm...@gmail.com> wrote:
>>>
>>> Hi There,
>>> I have a situation in which I need to connect to two different hosts. I need to be able to switch at runtime to a different host when one host goes down.
>>> What enterprise integration pattern should I use here? I don't know if I should use Dynamic Routing Or Load Balancing for this one.
>>> The message could only go to one place at a time. As long as the first one is up then I would have to go to it. But when it goes down, my application automatically needs to fall back to the other host system.
>>> In what way can I do this via Apache Camel .
>>> Thanks!!!
>>> Carlo
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Question On Dynamic Integration Pattern
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Jun 15, 2009 at 12:28 AM, Carlo Camerino<cm...@gmail.com> wrote:
> It seems that what I was looking for is present in Camel 2.0 which is
> the failover feature. I have a question though,
> Can I support failover and at the same time make it round robin? If
> one node is not functioning then I will no longer use that node.
Hi
There is a ticket in JIRA about ideas for improvments to the failover
load balancer.
We have thoughts of master/slave and having pluggable/selective
strategies for determine which slave to select etc.
So we are looking for use-cases and descriptions what you need. Please
feel free to add to this ticket.
https://issues.apache.org/activemq/browse/CAMEL-1471
But remember you can always extend or write your own logic as a Processor.
MyOwnLoadBalancer lb = new MyOwnLoadBalancer()
lb.addMaster("xxxx");
lb.addSlave("yyyy");
lb.addSlave("zzz");
lb.setSelection(RoundRobin);
And use .process(lb) in your route.
>
> Thanks
>
> On Mon, Jun 15, 2009 at 6:21 AM, Carlo Camerino <cm...@gmail.com> wrote:
>>
>> Hi There,
>> I have a situation in which I need to connect to two different hosts. I need to be able to switch at runtime to a different host when one host goes down.
>> What enterprise integration pattern should I use here? I don't know if I should use Dynamic Routing Or Load Balancing for this one.
>> The message could only go to one place at a time. As long as the first one is up then I would have to go to it. But when it goes down, my application automatically needs to fall back to the other host system.
>> In what way can I do this via Apache Camel .
>> Thanks!!!
>> Carlo
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Question On Dynamic Integration Pattern
Posted by Willem Jiang <wi...@gmail.com>.
You found the answer yourself.
For the failover support of the round robin, maybe we can add a flag in
the processor to tell if we need to skip that loadbalancer node when the
node is not functioning.
But according your requirement, you may need to use the failover feature :)
Willem
Carlo Camerino wrote:
> It seems that what I was looking for is present in Camel 2.0 which is
> the failover feature. I have a question though,
> Can I support failover and at the same time make it round robin? If
> one node is not functioning then I will no longer use that node.
>
> Thanks
>
> On Mon, Jun 15, 2009 at 6:21 AM, Carlo Camerino <cm...@gmail.com> wrote:
>> Hi There,
>> I have a situation in which I need to connect to two different hosts. I need to be able to switch at runtime to a different host when one host goes down.
>> What enterprise integration pattern should I use here? I don't know if I should use Dynamic Routing Or Load Balancing for this one.
>> The message could only go to one place at a time. As long as the first one is up then I would have to go to it. But when it goes down, my application automatically needs to fall back to the other host system.
>> In what way can I do this via Apache Camel .
>> Thanks!!!
>> Carlo
>
Re: Question On Dynamic Integration Pattern
Posted by Carlo Camerino <cm...@gmail.com>.
It seems that what I was looking for is present in Camel 2.0 which is
the failover feature. I have a question though,
Can I support failover and at the same time make it round robin? If
one node is not functioning then I will no longer use that node.
Thanks
On Mon, Jun 15, 2009 at 6:21 AM, Carlo Camerino <cm...@gmail.com> wrote:
>
> Hi There,
> I have a situation in which I need to connect to two different hosts. I need to be able to switch at runtime to a different host when one host goes down.
> What enterprise integration pattern should I use here? I don't know if I should use Dynamic Routing Or Load Balancing for this one.
> The message could only go to one place at a time. As long as the first one is up then I would have to go to it. But when it goes down, my application automatically needs to fall back to the other host system.
> In what way can I do this via Apache Camel .
> Thanks!!!
> Carlo
Re: Question On Dynamic Integration Pattern
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Carlo,
camel jms has a lot of options. I could imagine that you can find what
you need for your problem.
http://camel.apache.org/jms.html
For example it supports persistent delivery or transactions.
Besides that the jms server supports even more failover features.
http://activemq.apache.org/failover-transport-reference.html
Greetings
Christian
Carlo Camerino schrieb:
> are retries and interval already implemented in the current camel version?
>
> Thanks
>
> On Mon, Jun 15, 2009 at 2:17 PM, Carlo Camerino<cm...@gmail.com> wrote:
>
>> i updated jira issue.
>>
>> thanks a lot.
>>
>> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>
>>> hi,
>>>
>>> thanks for all the reply.
>>> I will be doing a little research on this.
>>> Especially the ones you gave me.
>>>
>>> thanks a lot
>>>
>>> On Mon, Jun 15, 2009 at 1:51 PM, Christian
>>> Schneider<ch...@die-schneider.net> wrote:
>>>
>>>> Hi Carlo,
>>>>
>>>> if you want round robin and failover you could think about using a simple
>>>> jms queue. If both your hosts listen on the queue then a jms server like
>>>> ActiveMQ will do round robin for all active listeners and automatically
>>>> leave out those that are not alive. Camel has very nice support for jms.
>>>>
>>>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>>>> One of the most important reasons for the decision was the above feature of
>>>> jms.
>>>>
>>>> Greetings
>>>>
>>>> Christian
>>>>
>>>>
>>>> Carlo Camerino schrieb:
>>>>
>>>>> Hi There,
>>>>> I have a situation in which I need to connect to two different hosts. I
>>>>> need
>>>>> to be able to switch at runtime to a different host when one host goes
>>>>> down.
>>>>> What enterprise integration pattern should I use here? I don't know if I
>>>>> should use Dynamic Routing Or Load Balancing for this one.
>>>>>
>>>>> The message could only go to one place at a time. As long as the first one
>>>>> is up then I would have to go to it. But when it goes down, my application
>>>>> automatically needs to fall back to the other host system.
>>>>>
>>>>> In what way can I do this via Apache Camel .
>>>>>
>>>>> Thanks!!!
>>>>>
>>>>> Carlo
>>>>>
>>>>>
>>>>>
>>>>
>
>
--
Christian Schneider
---
http://www.liquid-reality.de
Re: Question On Dynamic Integration Pattern
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Jun 15, 2009 at 10:59 AM, Carlo Camerino<cm...@gmail.com> wrote:
> it was taken from camel-1142, the parent of the issue that you said.
>
> Component/s: camel-core
> Affects Version/s: None
> Fix Version/s: 2.0-M1
>
> failover("http://frodo", "http://samwise",
> "file://UnProcessedMessages").retries(3).interval(1000).exponentialBackOff(false)
>
Ah okay.
No it does *not* support that.
Its documented here what it can
http://camel.apache.org/load-balancer.html
And yes its a bit simple at the moment but to be enhanced in Camel 2.1.
> On Mon, Jun 15, 2009 at 4:36 PM, Claus Ibsen<cl...@gmail.com> wrote:
>> On Mon, Jun 15, 2009 at 10:32 AM, Carlo Camerino<cm...@gmail.com> wrote:
>>> are retries and interval already implemented in the current camel version?
>> Can you be a bit more specific? where should it be implemented? And
>> which version of Camel?
>> And what do you mean with interval?
>>
>> Sorry I have many balls in the air so would help if the mails is a bit
>> more precise.
>>
>>
>>>
>>> Thanks
>>>
>>> On Mon, Jun 15, 2009 at 2:17 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>>> i updated jira issue.
>>>>
>>>> thanks a lot.
>>>>
>>>> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>>>> hi,
>>>>>
>>>>> thanks for all the reply.
>>>>> I will be doing a little research on this.
>>>>> Especially the ones you gave me.
>>>>>
>>>>> thanks a lot
>>>>>
>>>>> On Mon, Jun 15, 2009 at 1:51 PM, Christian
>>>>> Schneider<ch...@die-schneider.net> wrote:
>>>>>> Hi Carlo,
>>>>>>
>>>>>> if you want round robin and failover you could think about using a simple
>>>>>> jms queue. If both your hosts listen on the queue then a jms server like
>>>>>> ActiveMQ will do round robin for all active listeners and automatically
>>>>>> leave out those that are not alive. Camel has very nice support for jms.
>>>>>>
>>>>>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>>>>>> One of the most important reasons for the decision was the above feature of
>>>>>> jms.
>>>>>>
>>>>>> Greetings
>>>>>>
>>>>>> Christian
>>>>>>
>>>>>>
>>>>>> Carlo Camerino schrieb:
>>>>>>>
>>>>>>> Hi There,
>>>>>>> I have a situation in which I need to connect to two different hosts. I
>>>>>>> need
>>>>>>> to be able to switch at runtime to a different host when one host goes
>>>>>>> down.
>>>>>>> What enterprise integration pattern should I use here? I don't know if I
>>>>>>> should use Dynamic Routing Or Load Balancing for this one.
>>>>>>>
>>>>>>> The message could only go to one place at a time. As long as the first one
>>>>>>> is up then I would have to go to it. But when it goes down, my application
>>>>>>> automatically needs to fall back to the other host system.
>>>>>>>
>>>>>>> In what way can I do this via Apache Camel .
>>>>>>>
>>>>>>> Thanks!!!
>>>>>>>
>>>>>>> Carlo
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Question On Dynamic Integration Pattern
Posted by Carlo Camerino <cm...@gmail.com>.
it was taken from camel-1142, the parent of the issue that you said.
Component/s: camel-core
Affects Version/s: None
Fix Version/s: 2.0-M1
failover("http://frodo", "http://samwise",
"file://UnProcessedMessages").retries(3).interval(1000).exponentialBackOff(false)
On Mon, Jun 15, 2009 at 4:36 PM, Claus Ibsen<cl...@gmail.com> wrote:
> On Mon, Jun 15, 2009 at 10:32 AM, Carlo Camerino<cm...@gmail.com> wrote:
>> are retries and interval already implemented in the current camel version?
> Can you be a bit more specific? where should it be implemented? And
> which version of Camel?
> And what do you mean with interval?
>
> Sorry I have many balls in the air so would help if the mails is a bit
> more precise.
>
>
>>
>> Thanks
>>
>> On Mon, Jun 15, 2009 at 2:17 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>> i updated jira issue.
>>>
>>> thanks a lot.
>>>
>>> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>>> hi,
>>>>
>>>> thanks for all the reply.
>>>> I will be doing a little research on this.
>>>> Especially the ones you gave me.
>>>>
>>>> thanks a lot
>>>>
>>>> On Mon, Jun 15, 2009 at 1:51 PM, Christian
>>>> Schneider<ch...@die-schneider.net> wrote:
>>>>> Hi Carlo,
>>>>>
>>>>> if you want round robin and failover you could think about using a simple
>>>>> jms queue. If both your hosts listen on the queue then a jms server like
>>>>> ActiveMQ will do round robin for all active listeners and automatically
>>>>> leave out those that are not alive. Camel has very nice support for jms.
>>>>>
>>>>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>>>>> One of the most important reasons for the decision was the above feature of
>>>>> jms.
>>>>>
>>>>> Greetings
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> Carlo Camerino schrieb:
>>>>>>
>>>>>> Hi There,
>>>>>> I have a situation in which I need to connect to two different hosts. I
>>>>>> need
>>>>>> to be able to switch at runtime to a different host when one host goes
>>>>>> down.
>>>>>> What enterprise integration pattern should I use here? I don't know if I
>>>>>> should use Dynamic Routing Or Load Balancing for this one.
>>>>>>
>>>>>> The message could only go to one place at a time. As long as the first one
>>>>>> is up then I would have to go to it. But when it goes down, my application
>>>>>> automatically needs to fall back to the other host system.
>>>>>>
>>>>>> In what way can I do this via Apache Camel .
>>>>>>
>>>>>> Thanks!!!
>>>>>>
>>>>>> Carlo
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
Re: Question On Dynamic Integration Pattern
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Jun 15, 2009 at 10:32 AM, Carlo Camerino<cm...@gmail.com> wrote:
> are retries and interval already implemented in the current camel version?
Can you be a bit more specific? where should it be implemented? And
which version of Camel?
And what do you mean with interval?
Sorry I have many balls in the air so would help if the mails is a bit
more precise.
>
> Thanks
>
> On Mon, Jun 15, 2009 at 2:17 PM, Carlo Camerino<cm...@gmail.com> wrote:
>> i updated jira issue.
>>
>> thanks a lot.
>>
>> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
>>> hi,
>>>
>>> thanks for all the reply.
>>> I will be doing a little research on this.
>>> Especially the ones you gave me.
>>>
>>> thanks a lot
>>>
>>> On Mon, Jun 15, 2009 at 1:51 PM, Christian
>>> Schneider<ch...@die-schneider.net> wrote:
>>>> Hi Carlo,
>>>>
>>>> if you want round robin and failover you could think about using a simple
>>>> jms queue. If both your hosts listen on the queue then a jms server like
>>>> ActiveMQ will do round robin for all active listeners and automatically
>>>> leave out those that are not alive. Camel has very nice support for jms.
>>>>
>>>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>>>> One of the most important reasons for the decision was the above feature of
>>>> jms.
>>>>
>>>> Greetings
>>>>
>>>> Christian
>>>>
>>>>
>>>> Carlo Camerino schrieb:
>>>>>
>>>>> Hi There,
>>>>> I have a situation in which I need to connect to two different hosts. I
>>>>> need
>>>>> to be able to switch at runtime to a different host when one host goes
>>>>> down.
>>>>> What enterprise integration pattern should I use here? I don't know if I
>>>>> should use Dynamic Routing Or Load Balancing for this one.
>>>>>
>>>>> The message could only go to one place at a time. As long as the first one
>>>>> is up then I would have to go to it. But when it goes down, my application
>>>>> automatically needs to fall back to the other host system.
>>>>>
>>>>> In what way can I do this via Apache Camel .
>>>>>
>>>>> Thanks!!!
>>>>>
>>>>> Carlo
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Question On Dynamic Integration Pattern
Posted by Carlo Camerino <cm...@gmail.com>.
are retries and interval already implemented in the current camel version?
Thanks
On Mon, Jun 15, 2009 at 2:17 PM, Carlo Camerino<cm...@gmail.com> wrote:
> i updated jira issue.
>
> thanks a lot.
>
> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
>> hi,
>>
>> thanks for all the reply.
>> I will be doing a little research on this.
>> Especially the ones you gave me.
>>
>> thanks a lot
>>
>> On Mon, Jun 15, 2009 at 1:51 PM, Christian
>> Schneider<ch...@die-schneider.net> wrote:
>>> Hi Carlo,
>>>
>>> if you want round robin and failover you could think about using a simple
>>> jms queue. If both your hosts listen on the queue then a jms server like
>>> ActiveMQ will do round robin for all active listeners and automatically
>>> leave out those that are not alive. Camel has very nice support for jms.
>>>
>>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>>> One of the most important reasons for the decision was the above feature of
>>> jms.
>>>
>>> Greetings
>>>
>>> Christian
>>>
>>>
>>> Carlo Camerino schrieb:
>>>>
>>>> Hi There,
>>>> I have a situation in which I need to connect to two different hosts. I
>>>> need
>>>> to be able to switch at runtime to a different host when one host goes
>>>> down.
>>>> What enterprise integration pattern should I use here? I don't know if I
>>>> should use Dynamic Routing Or Load Balancing for this one.
>>>>
>>>> The message could only go to one place at a time. As long as the first one
>>>> is up then I would have to go to it. But when it goes down, my application
>>>> automatically needs to fall back to the other host system.
>>>>
>>>> In what way can I do this via Apache Camel .
>>>>
>>>> Thanks!!!
>>>>
>>>> Carlo
>>>>
>>>>
>>>
>>>
>>
>
Re: Question On Dynamic Integration Pattern
Posted by Carlo Camerino <cm...@gmail.com>.
i updated jira issue.
thanks a lot.
On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cm...@gmail.com> wrote:
> hi,
>
> thanks for all the reply.
> I will be doing a little research on this.
> Especially the ones you gave me.
>
> thanks a lot
>
> On Mon, Jun 15, 2009 at 1:51 PM, Christian
> Schneider<ch...@die-schneider.net> wrote:
>> Hi Carlo,
>>
>> if you want round robin and failover you could think about using a simple
>> jms queue. If both your hosts listen on the queue then a jms server like
>> ActiveMQ will do round robin for all active listeners and automatically
>> leave out those that are not alive. Camel has very nice support for jms.
>>
>> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
>> One of the most important reasons for the decision was the above feature of
>> jms.
>>
>> Greetings
>>
>> Christian
>>
>>
>> Carlo Camerino schrieb:
>>>
>>> Hi There,
>>> I have a situation in which I need to connect to two different hosts. I
>>> need
>>> to be able to switch at runtime to a different host when one host goes
>>> down.
>>> What enterprise integration pattern should I use here? I don't know if I
>>> should use Dynamic Routing Or Load Balancing for this one.
>>>
>>> The message could only go to one place at a time. As long as the first one
>>> is up then I would have to go to it. But when it goes down, my application
>>> automatically needs to fall back to the other host system.
>>>
>>> In what way can I do this via Apache Camel .
>>>
>>> Thanks!!!
>>>
>>> Carlo
>>>
>>>
>>
>>
>
Re: Question On Dynamic Integration Pattern
Posted by Carlo Camerino <cm...@gmail.com>.
hi,
thanks for all the reply.
I will be doing a little research on this.
Especially the ones you gave me.
thanks a lot
On Mon, Jun 15, 2009 at 1:51 PM, Christian
Schneider<ch...@die-schneider.net> wrote:
> Hi Carlo,
>
> if you want round robin and failover you could think about using a simple
> jms queue. If both your hosts listen on the queue then a jms server like
> ActiveMQ will do round robin for all active listeners and automatically
> leave out those that are not alive. Camel has very nice support for jms.
>
> In my company we do the complete SOA based on SOAP/JMS instead of SOAP/HTTP.
> One of the most important reasons for the decision was the above feature of
> jms.
>
> Greetings
>
> Christian
>
>
> Carlo Camerino schrieb:
>>
>> Hi There,
>> I have a situation in which I need to connect to two different hosts. I
>> need
>> to be able to switch at runtime to a different host when one host goes
>> down.
>> What enterprise integration pattern should I use here? I don't know if I
>> should use Dynamic Routing Or Load Balancing for this one.
>>
>> The message could only go to one place at a time. As long as the first one
>> is up then I would have to go to it. But when it goes down, my application
>> automatically needs to fall back to the other host system.
>>
>> In what way can I do this via Apache Camel .
>>
>> Thanks!!!
>>
>> Carlo
>>
>>
>
>
Re: Question On Dynamic Integration Pattern
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Carlo,
if you want round robin and failover you could think about using a
simple jms queue. If both your hosts listen on the queue then a jms
server like ActiveMQ will do round robin for all active listeners and
automatically leave out those that are not alive. Camel has very nice
support for jms.
In my company we do the complete SOA based on SOAP/JMS instead of
SOAP/HTTP. One of the most important reasons for the decision was the
above feature of jms.
Greetings
Christian
Carlo Camerino schrieb:
> Hi There,
> I have a situation in which I need to connect to two different hosts. I need
> to be able to switch at runtime to a different host when one host goes down.
> What enterprise integration pattern should I use here? I don't know if I
> should use Dynamic Routing Or Load Balancing for this one.
>
> The message could only go to one place at a time. As long as the first one
> is up then I would have to go to it. But when it goes down, my application
> automatically needs to fall back to the other host system.
>
> In what way can I do this via Apache Camel .
>
> Thanks!!!
>
> Carlo
>
>