Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 20 Jul 2013 14:04:49 +0000 (UTC)
From: "Zemian Deng (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12653140.1371454133671.85943.1374329089088@arcas>
In-Reply-To: <JIRA.12653140.1371454133671@arcas>
References: <JIRA.12653140.1371454133671@arcas>
Subject: [jira] [Commented] (CAMEL-6461) camel-quartz - Stateful job -
 Redeploying bundle/war and having changed endpoint uri issue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I noticed my patch has cause this test to fail: QuartzCronRouteWithSmallCacheTest

I am not familiar with the endpoint caching. Would anyone know how exactly does the endpoints are removed and should be recreated when caching is full? What methods are called on QuartzEndpoint when this happens?
 
                
> 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
>
>         Attachments: CAMEL-6461.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