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 (JIRA)" <ji...@apache.org> on 2013/07/22 17:20:48 UTC

[jira] [Assigned] (CAMEL-6461) camel-quartz - Stateful job - Redeploying bundle/war and having changed endpoint uri issue

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

Claus Ibsen reassigned CAMEL-6461:
----------------------------------

    Assignee: Claus Ibsen
    
> camel-quartz - Stateful job - Redeploying bundle/war and having changed endpoint uri issue
> ------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6461
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6461
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz
>    Affects Versions: 2.10.4
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.10.7, 2.11.2, 2.12.0
>
>         Attachments: CAMEL-6461.patch, CAMEL-6461-v2.patch
>
>
> See
> http://camel.465427.n5.nabble.com/In-came-quartz-route-after-bundle-update-jobs-are-not-triggred-tp5734196.html
> In these situations we should use job.name to name the job unique so when you change the endpoint uri and redeploy the apps/bundles, then camel-quartz can find the old job in the quartz persistent store.
> There may be logic needed to lookup using job.name as the unique name in these situations, and then allow endpoint uri options to change over time, such as the cron trigger etc. Which should be adjusted accordingly as well.

--
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: http://www.atlassian.com/software/jira