Hi, I have a similiar problem and I tried to track it down.
After some time of work and testing several possibilities I took a look at the Quartz 2.2.0 sources and at the migration guide from quartz to quartz2. On the quartz homepage in the Migration guide <http://quartz-scheduler.org/documentation/quartz-2.x/migration-guide> you find the following section: Example old code: New code: As you see, the setter for the durability is not used anymore. When taking a closer look into the JavaDoc it becomes clear that the setter for durablity was removed from Version 2.0 onwards. This here is the solution which can be found on the internet when you google the issue we are experiencing: The solution above will not work anymore, as the setter for the durability is not available anymore. See here <http://www.quartz-scheduler.org/api/2.0.0/index.html?org/quartz/JobDetail.html> The solution above is only aplicable if you use camel-quartz instead of camel-quartz2. I tried to use the option storeDurably in the route, but this is not working either, as this methode is in the JobBuilder (org.quartz.JobBuilder) instead of its being in the JobDetail (which is used by Camel-quartz). I think the changes were made to the JobDetails to have a comfortable Java DSL for creating quartz routes. Would this be worth raising a bug? Kind Regards, Francesca -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Quartz2-Clustering-fails-due-to-durable-jobs-has-anyone-got-tp5741030p5748096.html Sent from the Camel - Users mailing list archive at Nabble.com.
