Available as of Camel 2.12.0
The quartz2: component provides a scheduled delivery of messages using the Quartz Scheduler 2.x .
Each endpoint represents a different timer (in Quartz terms, a Trigger and JobDetail).
Maven users will need to add the following dependency to their
pom.xml for this component:
NOTE: Quartz 2.x API is not compatible with Quartz 1.x. If you need to remain on old Quartz 1.x, please
use the old Quartz component instead.
The component uses either a
CronTrigger or a
SimpleTrigger. If no cron expression is provided, the component uses a simple trigger. If no
groupName is provided, the quartz component uses the
Camel group name.
You can append query options to the URI in the following format,
SimpleTrigger: How many times should the timer repeat?
SimpleTrigger: The amount of time in milliseconds between repeated triggers. Must enable
Sets the job name.
Sets the job option with the
Sets the trigger option with the
Uses a Quartz
If it is true will fire the trigger when the route is start when using SimpleTrigger.
If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.
If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true.
Camel 2.12.4/2.13: Whether or not the job should remain stored after it is orphaned (no triggers point to it).
Camel 2.12.4/2.13: Instructs the scheduler whether or not the job should be re-executed if a 'recovery' or 'fail-over' situation is
|Camel 2.15.0: If it is true, JobDataMap uses the CamelContext name directly to reference the camel context, if it is false, JobDataMap uses use the CamelContext management name which could be changed during the deploy time.|
For example, the following routing rule will fire two timer events to the
stateful=true, the JobDataMap is re-persisted after every execution of the job, thus preserving state for the next execution.
Running in OSGi and having multiple bundles with quartz routes
If you run in OSGi such as Apache ServiceMix, or Apache Karaf, and have multiple bundles with Camel routes that start from Quartz2 endpoints, then make sure if you assign
id to the <camelContext> that this id is unique, as this is required by the
QuartzScheduler in the OSGi container. If you do not set any
id on <camelContext> then
a unique id is auto assigned, and there is no problem.
Configuring quartz.properties file
By default Quartz will look for a
quartz.properties file in the
org/quartz directory of the classpath. If you are using WAR deployments this means just drop the quartz.properties in
However the Camel Quartz2 component also allows you to configure properties:
You can configure a
File name of the properties to load from the classpath
To do this you can configure this in Spring XML as follows
Enabling Quartz scheduler in JMX
You need to configure the quartz scheduler properties to enable JMX.
That is typically setting the option
"org.quartz.scheduler.jmx.export" to a
true value in the configuration file.
From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled.
Starting the Quartz scheduler
The Quartz2 component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.
Seconds to wait before starting the quartz scheduler.
Whether or not the scheduler should be auto started.
To do this you can configure this in Spring XML as follows
If you use Quartz in clustered mode, e.g. the
JobStore is clustered. Then the Quartz2 component will not pause/remove triggers when a node is being stopped/shutdown. This allows the trigger to keep running on the other nodes in the cluster.
Note: When running in clustered node no checking is done to ensure unique job name/group for endpoints.
Camel adds the getters from the Quartz Execution Context as header values. The following headers are added:
fireTime header contains the
java.util.Date of when the exchange was fired.
Using Cron Triggers
Quartz supports Cron-like expressions for specifying timers in a handy format. You can use these expressions in the
cron URI parameter; though to preserve valid URI encoding we allow + to be used instead of spaces.
For example, the following will fire a message every five minutes starting at 12pm (noon) to 6pm on weekdays:
which is equivalent to using the cron expression
The following table shows the URI character encodings we use to preserve valid URI syntax:
Specifying time zone
The Quartz Scheduler allows you to configure time zone per trigger. For example to use a timezone of your country, then you can do as follows:
The timeZone value is the values accepted by
For example to use a cron based expression to poll for files every 2nd second, then a Camel route can be define simply as:
Notice we define the
scheduler=quartz2 to instruct Camel to use the Quartz2 based scheduler. Then we use
scheduler.xxx options to configure the scheduler. The Quartz2 scheduler requires the cron option to be set.
The following options is supported:
To use a custom Quartz scheduler. If none configure then the shared scheduler from the Quartz2 component is used.
Mandatory: To define the cron expression for triggering the polls.
To specify the trigger id. If none provided then an UUID is generated and used.
To specify the trigger group.
The time zone to use for the CRON trigger.
Important: Remember configuring these options from the endpoint URIs must be prefixed with
For example to configure the trigger id and group:
There is also a CRON scheduler in Spring, so you can use the following as well: