camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6067) Provider deleteJob=true|false as an option for Quartz component
Date Wed, 07 Aug 2013 14:28:48 GMT


Claus Ibsen commented on CAMEL-6067:

Ad 3)
The code comment explains why. You most likely not want misfires to fire if you have stopped
and started a server etc. Or at least you should be able to easily dictate what to do. 

So if you have a stateful job you may want to keep the trigger in the scheduler store, and
still stop / start servers in a controlled fashion, and not have misfires trigger if it was
started again. 

Not sure if there should be another option to fast-forward to now on startup, so ppl can turn
this on|off according to their needs.
> Provider deleteJob=true|false as an option for Quartz component
> ---------------------------------------------------------------
>                 Key: CAMEL-6067
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-quartz
>    Affects Versions: 2.10.2, 2.10.3
>            Reporter: Vishal
>            Priority: Minor
>             Fix For: 2.12.0, Future
>         Attachments: CAMEL-6067.path
> Although there is an option for defining stateful jobs in the quartz component via stateful=true,
the jobs created are eventually deleted when Camel shutsdown. 
> Please see,
> An option is needed to instruct Camel to not remove stateful jobs when coming down.

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

View raw message