camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Vahdat (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4900) Quartz component doesn't start with a persistent scheduler
Date Tue, 17 Jan 2012 08:26:45 GMT


Babak Vahdat commented on CAMEL-4900:

@Bryan would you have the possibility to provide a unit-test demonstrating the regression
failure you mentioned or provide maybe a snippet of your routing logic so that we can reproduce
this regression failure on the trunk. 
> Quartz component doesn't start with a persistent scheduler
> ----------------------------------------------------------
>                 Key: CAMEL-4900
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz
>    Affects Versions: 2.9.0
>         Environment: Java 1.6.0_29 64-bit, Mac OS X 10.7 and CentOS 6
>            Reporter: Bryan Keller
> I have scheduler persistence on but clustering is not turned on. When starting my app
the first time, it starts OK. After shutting down and staring a second time, an exception
is thrown and the app doesn't start up. This did not occur in 2.8.3. The following exception
> Caused by: org.quartz.SchedulerException: Trigger's related Job's name cannot be null
> 	at org.quartz.Trigger.validate( ~[quartz-1.8.5.jar:na]
> 	at org.quartz.core.QuartzScheduler.rescheduleJob( ~[quartz-1.8.5.jar:na]
> 	at org.quartz.impl.StdScheduler.rescheduleJob( ~[quartz-1.8.5.jar:na]
> 	at org.apache.camel.component.quartz.QuartzComponent.doAddJob(
> In 2.9.0, the code was changed here and this is where it craashes:
> {code}
> if (!isClustered()) {
>     trigger.setStartTime(Calendar.getInstance().getTime());
>     scheduler.rescheduleJob(trigger.getName(), trigger.getGroup(), trigger);
> }
> {code}
> My component definition looks like this:
> {code}
> <endpoint id="myschedule" uri="quartz://fmc/mycron=${myschedule.cron}&amp;stateful=true"
> {code}
> Again, this affects 2.9.0 but not 2.8.3. I have not found a workaround yet.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message