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: The timing of the timer component
Date Thu, 11 Mar 2010 05:48:37 GMT
On Thu, Mar 11, 2010 at 12:07 AM, huntc <huntc@mac.com> wrote:
>
> Hi there,
>
> Could it be that when the timer component is used it starts firing before
> all of the routes have been configured?
>

Yes see this page how to control startup order of routes
http://camel.apache.org/configuring-route-startup-ordering-and-autostartup.html

And the upcoming chapter 13 in the Camel in Action book, also covers
this as well.


> I had a race condition where on one machine Camel complained that route X
> (produced to by a timer consumer) wasn't established. On another machine
> though it was fine. Moving the code around so that route X was declared
> before the timer fixed the issue.
>
> Kind regards,
> Christopher
> --
> View this message in context: http://old.nabble.com/The-timing-of-the-timer-component-tp27857160p27857160.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Mime
View raw message