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

["Zemian Deng (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-6461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714101#comment-13714101 ] 

Zemian Deng commented on CAMEL-6461:
------------------------------------

Hello Claus,

I can confirm this problem. Further more, this problem only occur if we enabled Quartz clustering. For non-cluster config, the quartz endpoint will remove the job data upon restart.

I also tried by given job.name unique name, but still same problem. I think the problem is endpointUri is stored in the jobDetail data map instead of trigger data map.

I would propose to look up the endpoint by trigerName and jobName and avoid to store the endpointUri into the datamap to avoid this kind of mismatched problem.
                
> 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
>             Fix For: 2.10.7, 2.11.2, 2.12.0
>
>
> 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