Hi there, Could it be that when the timer component is used it starts firing before all of the routes have been configured?
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.
