You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2015/07/20 21:38:04 UTC

[jira] [Resolved] (CAMEL-8988) Can't manually trigger quartz2 jobs

     [ https://issues.apache.org/jira/browse/CAMEL-8988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey resolved CAMEL-8988.
------------------------------------
    Resolution: Fixed

> Can't manually trigger quartz2 jobs
> -----------------------------------
>
>                 Key: CAMEL-8988
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8988
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz2
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2.16.0, 2.15.3
>
>
> Using org.quartz.Scheduler.triggerJob to manually trigger jobs will result in an exception like:
> 2015-07-20 16:17:28,295 [amel-1_Worker-1] ERROR CamelJob                       - Failed to execute CamelJob.
> org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: quartz2://MyTimer?cron=05+00+00+*+*+%3F due to: Trigger key Camel.MyTimer is already in use by Endpoint[quartz2://MyTimer?cron=05+00+00+*+*+%3F]
> Problem is that CamelJob is having trouble with looking up the proper endpoint from a previously saved URI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)