Return-Path: 
 <users-return-40212-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0282BC26C
	for <apmail-camel-users-archive@www.apache.org>;
 Fri, 14 Jun 2013 08:47:55 +0000 (UTC)
Received: (qmail 34630 invoked by uid 500); 14 Jun 2013 08:47:54 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 34579 invoked by uid 500); 14 Jun 2013 08:47:54 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Delivered-To: moderator for users@camel.apache.org
Received: (qmail 36530 invoked by uid 99); 14 Jun 2013 07:52:46 -0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: error (nike.apache.org: encountered temporary error during SPF
 processing of domain of pradeepncs86@gmail.com)
Date: Fri, 14 Jun 2013 00:51:52 -0700 (PDT)
From: pradeep <pradeepncs86@gmail.com>
To: users@camel.apache.org
Message-ID: <1371196312147-5734196.post@n5.nabble.com>
Subject: In came-quartz route after bundle update jobs are not triggred.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


In came-quartz route after bundle update jobs are not triggred.
I created a small example for camel-quartz with persistence(Quatz mysql
database). My blueprint.xml looks like

<route id="CamelQuartzExampleRoute">
<from uri="CamelQuartzJob" />
<setBody>
<method ref="helloBean" method="hello"/>
</setBody>
<log message="The message contains $
{body}

"/>
<to uri="mock:result"/>
</route>

In the above route I used property placeholder CamelQuartzJob for quartz uri
and its value is configured from a configuration file. I deployed this
example in jboss fuse and it worked as expected means the job is stored in
quartz database and triggered for every 30 seconds. The actual issue is
1. I changed the quartz uri value configured in configuration file from
CamelQuartzJob=
quartz://DeleteRecord/DeleteRecordTimer?cron=0/30+?&stateful=true to
CamelQuartzJob=
quartz://DeleteRecord/DeleteRecordTimer?cron=0/60+?&stateful=true and then
did a bundle update for that example project.
2. The bundle started successfully but the scheduled job is not started for
every 60 seconds. From fuse logs I could see

12:13:00,014 | WARN | heduler_Worker-1 | CamelJob | 261 -
org.apache.camel.camel-quartz - 2.10.0.redhat-60024 | Cannot find existing
QuartzEndpoint with uri:
quartz://DeleteRecord/DeleteRecordTimer?cron=0%2F30+%3F&stateful=true.
Creating new endpoint instance.

I believe in camel-quartz we have to use route id or the endpoint id in the
quartz database instead of the URI. But not sure about the root cause.
Please guide me?




--
View this message in context: http://camel.465427.n5.nabble.com/In-came-quartz-route-after-bundle-update-jobs-are-not-triggred-tp5734196.html
Sent from the Camel - Users mailing list archive at Nabble.com.