On Mon, Jun 15, 2009 at 10:59 AM, Carlo Camerino<cmcamer...@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<claus.ib...@gmail.com> wrote:
>> On Mon, Jun 15, 2009 at 10:32 AM, Carlo Camerino<cmcamer...@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<cmcamer...@gmail.com> wrote:
>>>> i updated jira issue.
>>>>
>>>> thanks a lot.
>>>>
>>>> On Mon, Jun 15, 2009 at 2:07 PM, Carlo Camerino<cmcamer...@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

Reply via email to