Hi As you've already reported by your first post, only increasing the number of running VM's makes this exception to happen (from 2 to 7). This CAN be a hint for a race-condition somewhere. There was a similar problem being reported while ago:
https://issues.apache.org/jira/browse/CAMEL-6686 The only reason why we could fix that was because we could reproduce the same exception inside a test, which is now added to the code base of this Camel module. In your case I was NOT able to do the same. If you could somehow provide a test or a sample project then we could dig into this to see if we can find the root cause of the problem and probably fix it. There's also the following Camel test module you could make use of for this: http://camel.apache.org/blueprint-testing.html Babak lakshmi.prashant wrote > Hi, > > Can you kindly explain why the route starts failing after running for > sometime.. > Why is the doAddJob() getting called, after few runs of a schedule have > already tun, as reported in the exception? > The race condition can happen only at the start of the route, while > scheduling the quartz job. But it gets reported after few runs in the > below exception trace: <http://camel.465427.n5.nabble.com/file/n5743232/Route_Stoping_After_fewruns.png> > > 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) -- View this message in context: http://camel.465427.n5.nabble.com/Camel-quartz-misfires-and-route-not-getting-run-triggered-after-exception-ObjectAlreadyExistsExceptin-tp5739997p5743238.html Sent from the Camel - Users mailing list archive at Nabble.com.
