camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ingo Düppe (JIRA) <j...@apache.org>
Subject [jira] Updated: (CAMEL-3079) job rescheduling and clustering does not work properly
Date Wed, 25 Aug 2010 15:28:47 GMT

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

Ingo Düppe updated CAMEL-3079:
------------------------------

    Attachment: camel-quartz.patch

Patch is for the current trunk version of 2.5-SNAPSHOT.

> job rescheduling and clustering does not work properly 
> -------------------------------------------------------
>
>                 Key: CAMEL-3079
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3079
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-quartz
>    Affects Versions: 2.4.0
>         Environment: Database cluster scenario
>            Reporter: Ingo Düppe
>             Fix For: 2.5.0
>
>         Attachments: camel-quartz.patch
>
>
> Currently stateful cron jobs are identified by their group name, job name and the cron
expression. This prevents an easy rescheduling of cron jobs. For instance, stopping a camel
context, rescheduling the cron job by editing the cron expressing and restart will end up
in an exception. This will happen because the rescheduled job will be added as an additional
job. The already existing job will produce an exception because the corresponding endpoint
doesn't exist anymore. The previous solution deleting all triggers on shutdown doesn't work
in a cluster scenario. 
> I suggest to identify cron jobs only by their group and job name. On startup it will
check if a trigger already exists and check if the cron expression has changed. If so it will
be rescheduled.
> Also the current explicit resuming of stateful jobs will produce an exception during
startup, because the scheduler automatically finds and resumes stored triggers. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message