On Fri, Feb 8, 2013 at 11:04 PM, vishal1981
<vishal.changr...@ericsson.com> wrote:
> Hi,
> I am using Quartz as my starting endponig. I have defined the the route as
> follows,
>
> from("quartz://myTimer?trigger.repeatInterval=120000&trigger.repeatCount=-1&stateful=true")
> .log("Test");
> When Camel comes up I do see an entry being created in the database for the
> trigger and for the job. However once my test finishes and Camel is stopped
> that entry is removed from the database and I see in the logs that the
> quartz job was stopped and the trigger was deleted - 'DEBUG - Deleting job
> using trigger: Camel/myTimer'.
> I would like the trigger to persist so that it can be used to calculate a
> misfire next time when the test is re-ran and Camel comes up.
> Is there a way to do that?
>
No.
Fell free to log a JIRA ticket for an new feature, so we can add an
option deleteJob=true|false, so people can control this.
http://camel.apache.org/support
> thanks,
> -v-
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Quartz-triggers-being-deleted-when-shutting-down-Camel-tp5727257.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
