Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
Quartz ComponentThe quartz: component provides a scheduled delivery of messages using the Quartz Scheduler 1.x . If you are using Quartz 2.x then from Camel 2.12 onwards there is a Quartz2 component you should use Maven users will need to add the following dependency to their <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-quartz</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI formatquartz://timerName?options quartz://groupName/timerName?options quartz://groupName/timerName?cron=expression quartz://timerName?cron=expression The component uses either a You can append query options to the URI in the following format, Options
For example, the following routing rule will fire two timer events to the Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20 When using a StatefulJob, 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 Quartz endpoints, then make sure if you assign Configuring quartz.properties fileBy default Quartz will look for a However the Camel Quartz component also allows you to configure properties:
To do this you can configure this in Spring XML as follows <bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent"> <property name="propertiesFile" value="com/mycompany/myquartz.properties"/> </bean> Enabling Quartz scheduler in JMXYou need to configure the quartz scheduler properties to enable JMX. From Camel 2.13 onwards Camel will automatic set this option to true, unless explicit disabled. Starting the Quartz schedulerAvailable as of Camel 2.4 The Quartz component offers an option to let the Quartz scheduler be started delayed, or not auto started at all.
To do this you can configure this in Spring XML as follows <bean id="quartz" class="org.apache.camel.component.quartz.QuartzComponent"> <property name="startDelayedSeconds" value="5"/> </bean> ClusteringAvailable as of Camel 2.4 If you use Quartz in clustered mode, e.g. the Note: When running in clustered node no checking is done to ensure unique job name/group for endpoints. Message HeadersCamel adds the getters from the Quartz Execution Context as header values. The following headers are added: The Using Cron TriggersQuartz supports Cron-like expressions for specifying timers in a handy format. You can use these expressions in the For example, the following will fire a message every five minutes starting at 12pm (noon) to 6pm on weekdays: from("quartz://myGroup/myTimerName?cron=0+0/5+12-18+?+*+MON-FRI").to("activemq:Totally.Rocks"); which is equivalent to using the cron expression 0 0/5 12-18 ? * MON-FRI The following table shows the URI character encodings we use to preserve valid URI syntax:
Specifying time zoneAvailable as of Camel 2.8.1 quartz://groupName/timerName?cron=0+0/5+12-18+?+*+MON-FRI&trigger.timeZone=Europe/Stockholm The timeZone value is the values accepted by In Camel 2.8.0 or older versions you would have to provide your custom |