You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/16 11:23:39 UTC
[jira] [Resolved] (CAMEL-4900) Quartz component doesn't start with
a persistent scheduler
[ https://issues.apache.org/jira/browse/CAMEL-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4900.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9.2
2.10.0
2.8.5
Assignee: Claus Ibsen (was: Hadrian Zbarcea)
> Quartz component doesn't start with a persistent scheduler
> ----------------------------------------------------------
>
> Key: CAMEL-4900
> URL: https://issues.apache.org/jira/browse/CAMEL-4900
> Project: Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.8.4, 2.9.0
> Environment: Java 1.6.0_29 64-bit, Mac OS X 10.7 and CentOS 6
> Reporter: Bryan Keller
> Assignee: Claus Ibsen
> Fix For: 2.8.5, 2.10.0, 2.9.2
>
> Attachments: quartztest.zip
>
>
> 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 occurs:
> Caused by: org.quartz.SchedulerException: Trigger's related Job's name cannot be null
> at org.quartz.Trigger.validate(Trigger.java:955) ~[quartz-1.8.5.jar:na]
> at org.quartz.core.QuartzScheduler.rescheduleJob(QuartzScheduler.java:982) ~[quartz-1.8.5.jar:na]
> at org.quartz.impl.StdScheduler.rescheduleJob(StdScheduler.java:302) ~[quartz-1.8.5.jar:na]
> at org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:233) ~[camel-quartz-2.9.0.jar:2.9.0]
> 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}&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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira