camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Running routes blocks timer event
Date Mon, 25 Nov 2013 14:51:41 GMT
Use different timer names, eg timer:bar etc

On Mon, Nov 25, 2013 at 3:25 PM, martin11 <mato.krajcir@gmail.com> wrote:
> Hello,
>
> I`m using camel ver. 2.11.0. I have multiple routes triggered by timer
> componnet like this:
>
> <camel:route id="route1">
>     <camel:from uri="timer://foo?fixedRate=true&amp;period={{period}}"/>
>     ...my processing...
> </camel:route>
>
> <camel:route id="route2">
>     <camel:from uri="timer://foo?fixedRate=true&amp;period={{period}}"/>
>     ...my processing...
> </camel:route>
>
> So when route1 running too long, it blocks processing from route2. Timer
> event is not generated until route1 is not finished.
> And routes are running step by step according to timers.
>
> I also tried wireTap to create new thread.
> <camel:route id="route1">
>     <camel:from uri="timer://foo?fixedRate=true&amp;period={{period}}"/>
>     <camel:wireTap copy="false" uri="direct:my-processing"/>
> </camel:route>
> But when "direct:my-processing" is running too long (aprox. 30min) and my
> period is 60s it generate multiple threads of my-processing route which is
> undesirable.
>
> What is the right way for paralell processing multiple timer events?
>
> Thanks.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Running-routes-blocks-timer-event-tp5743801.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message