The timer: component is used to generate message exchanges when a timer fires You can only consume events from this endpoint.
name is the name of the
Timer object, which is created and shared across endpoints. So if you use the same name for all your timer endpoints, only one
Timer object and thread will be used.
You can append query options to the URI in the following format,
Note: The IN body of the generated exchange is
See also the Quartz component that supports much more advanced scheduling.
Specify time in human friendly format
In Camel 2.3 onwards you can specify the time in human friendly syntax.
When the timer is fired, it adds the following information as properties to the
When the timer is fired, it adds the following information as headers to the IN message
To set up a route that generates an event every 60 seconds:
Instead of 60000 you can use period=60s which is more friendly to read.
And the route in Spring DSL:
Firing as soon as possible
Available as of Camel 2.17
You may want to fire messages in a Camel route as soon as possible you can use a negative delay:
In this way the timer will fire messages immediately.
You can also specify a repeatCount parameter in conjunction with a negative delay to stop firing messages after a fixed number has been reached.
If you don't specify a repeatCount then the timer will continue firing messages until the route will be stopped.
Firing only once
Available as of Camel 2.8
You may want to fire a message in a Camel route only once, such as when starting the route. To do that you use the repeatCount option as shown: