Hi Were you able to find the root cause of the problem here? If not:
- Which exact Quartz 1.x version do you make use of? - Can you reproduce this with the latest Camel 2.12.1 version? - And CAMEL-5994 is already fixed so this should not cause any problem for you - Also looking at the stacktrace I think Quartz has not been setup properly in Cluster-Mode (see org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232) on the call-stack)... Did you set the org.quartz.jobStore.isClustered and org.quartz.jobStore.clusterCheckinInterval properties appropriately? - As you run inside OSGi but assign the id of <camelContext> by yourself (e.g. context4), have you seen the blue-box about this here http://camel.apache.org/quartz Babak lakshmi.prashant wrote > Hi, > > I am running camel quartz (2.10.4) & quartz has been set-up in clustered > mode. The clocks in the cluster are synchronized. > > I have set-up a trigger to run every 1 minute, via the camel-quartz > end-point in my route. > > a) it works fine if quartz is not set up in clustered mode (uses > RAMJobstore). > > b) If quartz is set up in clustred mode, it was working fine when there > were only 2 nodes in the cluster. > Sometimes, instead of every 1 minute, the runs used to get fired > every 2 minutes over a time-window, but it seemed to stabilize and run > fine. > > c) After I increased the number of VM's in the cluster (to ~7 VM's), I > faced misfires.. > > i) The routes used to be triggered correctly for sometime and then > stop working altogether.. > ii) The below exception has been logged in 1 (or) more VM's in the > cluster, after which the camel endpoints seemed to not fire at all. PFA > the depiction of misfires from camel. > > Note: This issue is noticed in 2.11 camel as well. Is this related to > https://issues.apache.org/jira/browse/CAMEL-5994... And has this not been > fixed till now? > > Kindly help. > > Thanks, > Lakshmi > > Exception Trace: > > ERROR#org.apache.camel.blueprint.BlueprintCamelContext##anonymous#Blueprint > Extender: 3##avatarcl#aq4appaq4t#iflmap#null#null#Error occurred during > starting Camel: CamelContext(context4) due Unable to store Trigger with > name: 'schedule3' and group: 'Camel', because one already exists with this > identification.org.quartz.ObjectAlreadyExistsException: Unable to store > Trigger with name: 'schedule3' and group: 'Camel', because one already > exists with this identification. > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1200) > at > org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1072) > at > org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:3716) > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3788) > at > org.quartz.impl.jdbcjobstore.JobStoreTX.executeInLock(JobStoreTX.java:90) > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3712) > at > org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigger(JobStoreSupport.java:1059) > at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:822) > at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243) > at > org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232) > at > org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:222) > at > org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:81) > at > org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:213) > at > org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39) > at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) > at > org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1819) > at > org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:2113) > at > org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:2049) > at > org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:1979) > at > org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:1758) > at > org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1633) > at > org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1500) > > <http://camel.465427.n5.nabble.com/file/n5739997/FailedRuns.jpg> <http://camel.465427.n5.nabble.com/file/n5739997/runs_successful_with_2_VMs.jpg> <http://camel.465427.n5.nabble.com/file/n5739997/some_runs_misfiring_fire_in_2_mins.jpg> -- View this message in context: http://camel.465427.n5.nabble.com/Camel-quartz-misfires-and-route-not-getting-run-triggered-after-exception-ObjectAlreadyExistsExceptin-tp5739997p5740345.html Sent from the Camel - Users mailing list archive at Nabble.com.
