Re: camel-quartz is misfiring on startup

[Santiago Acosta]

Thanks Claus! I had completely overlooked such simple ootb solutions!
However, our current solution is working quite well so we will not be
revisiting for the time being.

Thanks again. There is so much more to learn and test

On Tue, Jan 11, 2022 at 11:59 AM Claus Ibsen  wrote:

> Hi
>
> For quartz then one of its only benefits is its cron support.
> If you just want to trigger every X interval, then use camel-timer or
> camel-scheduler (latter more advanced).
>
> And for cron, there is in fact also camel-spring where they have cron
> support.
>
> On Tue, Jan 11, 2022 at 11:50 AM Santiago Acosta
>  wrote:
> >
> > Thanks for the info Karen, but I am sad to say we had to move on to use
> > something else (I think VertX which also has integrations with Camel).
> I'll
> > keep this close to the chest when the opportunity to use Camel+Quartz
> comes
> > around again.
> >
> > I'll keep an eye on https://issues.apache.org/jira/browse/CAMEL-17446
> >
> > On Thu, Jan 6, 2022 at 4:25 PM Karen Lease 
> wrote:
> >
> > > Hi Santiago,
> > >
> > > Sorry for the late reply, but it seems no one else picked up on this
> yet.
> > > I think the behavior you see is related to the time between the
> creation
> > > of the job trigger in Quartz and when Camel finishes initializing and
> > > the Quartz scheduler is actually started.
> > >
> > > The initial fire time of the trigger for your job is set to the time
> > > when the trigger is created, not when the Quartz scheduler is actually
> > > started.
> > > Based on your logs and the Camel Quartz code, the trigger is created
> > > between the following 2 log messages, so between 19:54:47,514 and
> 47,545.
> > >
> > >  > ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
> > >  > scheduler version: 2.3.2
> > >  > ...:47,545 INFO  [main] o.a.c.c.quartz.QuartzEndpoint  - Job
> > >  > Camel_camel-1.resolver (triggerType=SimpleTriggerImpl,
> > >  > jobClass=StatefulCamelJob) is scheduled. Next fire date is Thu Dec
> 16
> > >  > 19:54:47 WET 2021
> > >
> > > Unfortunately the last message does not show the milliseconds in the
> > > start date, but we can see it is sometime in the second 19:54:47.
> > >
> > > It takes another 435 ms for Camel to finish its work and actually start
> > > the Quartz scheduler at 19:54:47,980:
> > >  > ...:47,979 INFO  [main] o.a.c.c.quartz.QuartzComponent -
> Starting
> > >  > scheduler.
> > >  > ...:47,980 INFO  [main] o.quartz.core.QuartzScheduler  -
> Scheduler
> > >  > DefaultQuartzScheduler-camel-1_$_NON_CLUSTERED started.
> > >
> > > Quartz fires the first event as soon as possible since the start time
> > > has already passed:
> > >  > ...:48,027 INFO  [Worker-1] quartz-daemon  - QUARTZ
> > >
> > > Adding 1200 ms to the possible start time range, the second one should
> > > have fired between 19:54:48,714 and 48,745 and it is fired at 48,722.
> > >  > ...:48,722 INFO  [Worker-2] quartz-daemon  - QUARTZ
> > >
> > >
> > > Set the logging level to DEBUG on
> > > org.apache.camel.component.quartz.QuartzEndpoint to see more details
> > > about the trigger creation but the behavior seems consistent.
> > >
> > > Unfortunately, if I correctly understand the code, setting
> > > triggerStartDelay to a postive number to account for the delay in
> > > starting the scheduler does not appear to work, since it sets the start
> > > time of the trigger only if it is *less* than 0 which seems
> > > counter-intuitive.
> > >
> > > In QuartzEndpoint.createTrigger():
> > > if (getComponent().getScheduler().isStarted() || triggerStartDelay <
> 0) {
> > >  triggerBuilder.startAt(new Date(System.currentTimeMillis() +
> > > triggerStartDelay));
> > > }
> > >
> > > I hope this helps or at least explains the behavior.
> > > I created https://issues.apache.org/jira/browse/CAMEL-17446 related to
> > > the points I mentioned.
> > >
> > >
> > >
> > > On 16/12/2021 21:20, Santiago Acosta wrote:
> > > > Camel 3.13 (but I also tried 3.6 and results are worse)
> > > >
> > > > I have an issue where a quartz route is misfiring at the beginning
> of the
> > > > startup. I ran some standalone Quartz scheduler with a simple job and
> > > > trigger and it works as expected, even with a small interval
> (<200ms).
> > > >
> > > > In the case of Camel, the interval is not being respected in the
> first
> > > few
> > > > exchanges.
> > > >
> > > > Notice at the end of the log how the first QUARTZ log entries are
> piled
> > > > together (interval 1200). If I shorten the interval I can pile them
> up
> > > even
> > > > more (3 entries in 100ms with interval 200ms)
> > > >
> > >
> > > > ...:47,318 INFO  [main] o.q.simpl.SimpleThreadPool - Job
> > > execution
> > > > threads will use class loader of thread: main
> > > > ...:47,332 INFO  [main] o.q.core.SchedulerSignalerImpl -
> Initialized
> > > > Scheduler Signaller of type: class
> org.quartz.core.SchedulerSignalerImpl
> > > > ...:47,333 INFO  [main] 

Re: camel-quartz is misfiring on startup

[Claus Ibsen]

Hi

For quartz then one of its only benefits is its cron support.
If you just want to trigger every X interval, then use camel-timer or
camel-scheduler (latter more advanced).

And for cron, there is in fact also camel-spring where they have cron support.

On Tue, Jan 11, 2022 at 11:50 AM Santiago Acosta
 wrote:
>
> Thanks for the info Karen, but I am sad to say we had to move on to use
> something else (I think VertX which also has integrations with Camel). I'll
> keep this close to the chest when the opportunity to use Camel+Quartz comes
> around again.
>
> I'll keep an eye on https://issues.apache.org/jira/browse/CAMEL-17446
>
> On Thu, Jan 6, 2022 at 4:25 PM Karen Lease  wrote:
>
> > Hi Santiago,
> >
> > Sorry for the late reply, but it seems no one else picked up on this yet.
> > I think the behavior you see is related to the time between the creation
> > of the job trigger in Quartz and when Camel finishes initializing and
> > the Quartz scheduler is actually started.
> >
> > The initial fire time of the trigger for your job is set to the time
> > when the trigger is created, not when the Quartz scheduler is actually
> > started.
> > Based on your logs and the Camel Quartz code, the trigger is created
> > between the following 2 log messages, so between 19:54:47,514 and 47,545.
> >
> >  > ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
> >  > scheduler version: 2.3.2
> >  > ...:47,545 INFO  [main] o.a.c.c.quartz.QuartzEndpoint  - Job
> >  > Camel_camel-1.resolver (triggerType=SimpleTriggerImpl,
> >  > jobClass=StatefulCamelJob) is scheduled. Next fire date is Thu Dec 16
> >  > 19:54:47 WET 2021
> >
> > Unfortunately the last message does not show the milliseconds in the
> > start date, but we can see it is sometime in the second 19:54:47.
> >
> > It takes another 435 ms for Camel to finish its work and actually start
> > the Quartz scheduler at 19:54:47,980:
> >  > ...:47,979 INFO  [main] o.a.c.c.quartz.QuartzComponent - Starting
> >  > scheduler.
> >  > ...:47,980 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
> >  > DefaultQuartzScheduler-camel-1_$_NON_CLUSTERED started.
> >
> > Quartz fires the first event as soon as possible since the start time
> > has already passed:
> >  > ...:48,027 INFO  [Worker-1] quartz-daemon  - QUARTZ
> >
> > Adding 1200 ms to the possible start time range, the second one should
> > have fired between 19:54:48,714 and 48,745 and it is fired at 48,722.
> >  > ...:48,722 INFO  [Worker-2] quartz-daemon  - QUARTZ
> >
> >
> > Set the logging level to DEBUG on
> > org.apache.camel.component.quartz.QuartzEndpoint to see more details
> > about the trigger creation but the behavior seems consistent.
> >
> > Unfortunately, if I correctly understand the code, setting
> > triggerStartDelay to a postive number to account for the delay in
> > starting the scheduler does not appear to work, since it sets the start
> > time of the trigger only if it is *less* than 0 which seems
> > counter-intuitive.
> >
> > In QuartzEndpoint.createTrigger():
> > if (getComponent().getScheduler().isStarted() || triggerStartDelay < 0) {
> >  triggerBuilder.startAt(new Date(System.currentTimeMillis() +
> > triggerStartDelay));
> > }
> >
> > I hope this helps or at least explains the behavior.
> > I created https://issues.apache.org/jira/browse/CAMEL-17446 related to
> > the points I mentioned.
> >
> >
> >
> > On 16/12/2021 21:20, Santiago Acosta wrote:
> > > Camel 3.13 (but I also tried 3.6 and results are worse)
> > >
> > > I have an issue where a quartz route is misfiring at the beginning of the
> > > startup. I ran some standalone Quartz scheduler with a simple job and
> > > trigger and it works as expected, even with a small interval (<200ms).
> > >
> > > In the case of Camel, the interval is not being respected in the first
> > few
> > > exchanges.
> > >
> > > Notice at the end of the log how the first QUARTZ log entries are piled
> > > together (interval 1200). If I shorten the interval I can pile them up
> > even
> > > more (3 entries in 100ms with interval 200ms)
> > >
> >
> > > ...:47,318 INFO  [main] o.q.simpl.SimpleThreadPool - Job
> > execution
> > > threads will use class loader of thread: main
> > > ...:47,332 INFO  [main] o.q.core.SchedulerSignalerImpl - Initialized
> > > Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
> > > ...:47,333 INFO  [main] o.quartz.core.QuartzScheduler  - Quartz
> > > Scheduler v.2.3.2 created.
> > > ...:47,334 INFO  [main] org.quartz.simpl.RAMJobStore   - RAMJobStore
> > > initialized.
> > > ...:47,514 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
> > > meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler-camel-1'
> > with
> > > instanceId 'NON_CLUSTERED'
> > >Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
> > >NOT STARTED.
> > >Currently in standby mode.
> > >Number of jobs 

Re: camel-quartz is misfiring on startup

[Santiago Acosta]

Thanks for the info Karen, but I am sad to say we had to move on to use
something else (I think VertX which also has integrations with Camel). I'll
keep this close to the chest when the opportunity to use Camel+Quartz comes
around again.

I'll keep an eye on https://issues.apache.org/jira/browse/CAMEL-17446

On Thu, Jan 6, 2022 at 4:25 PM Karen Lease  wrote:

> Hi Santiago,
>
> Sorry for the late reply, but it seems no one else picked up on this yet.
> I think the behavior you see is related to the time between the creation
> of the job trigger in Quartz and when Camel finishes initializing and
> the Quartz scheduler is actually started.
>
> The initial fire time of the trigger for your job is set to the time
> when the trigger is created, not when the Quartz scheduler is actually
> started.
> Based on your logs and the Camel Quartz code, the trigger is created
> between the following 2 log messages, so between 19:54:47,514 and 47,545.
>
>  > ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
>  > scheduler version: 2.3.2
>  > ...:47,545 INFO  [main] o.a.c.c.quartz.QuartzEndpoint  - Job
>  > Camel_camel-1.resolver (triggerType=SimpleTriggerImpl,
>  > jobClass=StatefulCamelJob) is scheduled. Next fire date is Thu Dec 16
>  > 19:54:47 WET 2021
>
> Unfortunately the last message does not show the milliseconds in the
> start date, but we can see it is sometime in the second 19:54:47.
>
> It takes another 435 ms for Camel to finish its work and actually start
> the Quartz scheduler at 19:54:47,980:
>  > ...:47,979 INFO  [main] o.a.c.c.quartz.QuartzComponent - Starting
>  > scheduler.
>  > ...:47,980 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
>  > DefaultQuartzScheduler-camel-1_$_NON_CLUSTERED started.
>
> Quartz fires the first event as soon as possible since the start time
> has already passed:
>  > ...:48,027 INFO  [Worker-1] quartz-daemon  - QUARTZ
>
> Adding 1200 ms to the possible start time range, the second one should
> have fired between 19:54:48,714 and 48,745 and it is fired at 48,722.
>  > ...:48,722 INFO  [Worker-2] quartz-daemon  - QUARTZ
>
>
> Set the logging level to DEBUG on
> org.apache.camel.component.quartz.QuartzEndpoint to see more details
> about the trigger creation but the behavior seems consistent.
>
> Unfortunately, if I correctly understand the code, setting
> triggerStartDelay to a postive number to account for the delay in
> starting the scheduler does not appear to work, since it sets the start
> time of the trigger only if it is *less* than 0 which seems
> counter-intuitive.
>
> In QuartzEndpoint.createTrigger():
> if (getComponent().getScheduler().isStarted() || triggerStartDelay < 0) {
>  triggerBuilder.startAt(new Date(System.currentTimeMillis() +
> triggerStartDelay));
> }
>
> I hope this helps or at least explains the behavior.
> I created https://issues.apache.org/jira/browse/CAMEL-17446 related to
> the points I mentioned.
>
>
>
> On 16/12/2021 21:20, Santiago Acosta wrote:
> > Camel 3.13 (but I also tried 3.6 and results are worse)
> >
> > I have an issue where a quartz route is misfiring at the beginning of the
> > startup. I ran some standalone Quartz scheduler with a simple job and
> > trigger and it works as expected, even with a small interval (<200ms).
> >
> > In the case of Camel, the interval is not being respected in the first
> few
> > exchanges.
> >
> > Notice at the end of the log how the first QUARTZ log entries are piled
> > together (interval 1200). If I shorten the interval I can pile them up
> even
> > more (3 entries in 100ms with interval 200ms)
> >
>
> > ...:47,318 INFO  [main] o.q.simpl.SimpleThreadPool - Job
> execution
> > threads will use class loader of thread: main
> > ...:47,332 INFO  [main] o.q.core.SchedulerSignalerImpl - Initialized
> > Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
> > ...:47,333 INFO  [main] o.quartz.core.QuartzScheduler  - Quartz
> > Scheduler v.2.3.2 created.
> > ...:47,334 INFO  [main] org.quartz.simpl.RAMJobStore   - RAMJobStore
> > initialized.
> > ...:47,514 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
> > meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler-camel-1'
> with
> > instanceId 'NON_CLUSTERED'
> >Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
> >NOT STARTED.
> >Currently in standby mode.
> >Number of jobs executed: 0
> >Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10
> threads.
> >Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
> support
> > persistence. and is not clustered.
> >
> > ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
> > scheduler 'DefaultQuartzScheduler-camel-1' initialized from an externally
> > provided properties instance.
> > ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
> > scheduler version: 2.3.2
> > ...:47,545 INFO  [main 

Re: camel-quartz is misfiring on startup

[Karen Lease]

Hi Santiago,

Sorry for the late reply, but it seems no one else picked up on this yet.
I think the behavior you see is related to the time between the creation 
of the job trigger in Quartz and when Camel finishes initializing and 
the Quartz scheduler is actually started.


The initial fire time of the trigger for your job is set to the time 
when the trigger is created, not when the Quartz scheduler is actually 
started.
Based on your logs and the Camel Quartz code, the trigger is created 
between the following 2 log messages, so between 19:54:47,514 and 47,545.


> ...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
> scheduler version: 2.3.2
> ...:47,545 INFO  [main] o.a.c.c.quartz.QuartzEndpoint  - Job
> Camel_camel-1.resolver (triggerType=SimpleTriggerImpl,
> jobClass=StatefulCamelJob) is scheduled. Next fire date is Thu Dec 16
> 19:54:47 WET 2021

Unfortunately the last message does not show the milliseconds in the 
start date, but we can see it is sometime in the second 19:54:47.


It takes another 435 ms for Camel to finish its work and actually start 
the Quartz scheduler at 19:54:47,980:

> ...:47,979 INFO  [main] o.a.c.c.quartz.QuartzComponent - Starting
> scheduler.
> ...:47,980 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
> DefaultQuartzScheduler-camel-1_$_NON_CLUSTERED started.

Quartz fires the first event as soon as possible since the start time 
has already passed:

> ...:48,027 INFO  [Worker-1] quartz-daemon  - QUARTZ

Adding 1200 ms to the possible start time range, the second one should 
have fired between 19:54:48,714 and 48,745 and it is fired at 48,722.

> ...:48,722 INFO  [Worker-2] quartz-daemon  - QUARTZ


Set the logging level to DEBUG on 
org.apache.camel.component.quartz.QuartzEndpoint to see more details 
about the trigger creation but the behavior seems consistent.


Unfortunately, if I correctly understand the code, setting 
triggerStartDelay to a postive number to account for the delay in 
starting the scheduler does not appear to work, since it sets the start 
time of the trigger only if it is *less* than 0 which seems 
counter-intuitive.


In QuartzEndpoint.createTrigger():
if (getComponent().getScheduler().isStarted() || triggerStartDelay < 0) {
triggerBuilder.startAt(new Date(System.currentTimeMillis() + 
triggerStartDelay));

}

I hope this helps or at least explains the behavior.
I created https://issues.apache.org/jira/browse/CAMEL-17446 related to 
the points I mentioned.




On 16/12/2021 21:20, Santiago Acosta wrote:

Camel 3.13 (but I also tried 3.6 and results are worse)

I have an issue where a quartz route is misfiring at the beginning of the
startup. I ran some standalone Quartz scheduler with a simple job and
trigger and it works as expected, even with a small interval (<200ms).

In the case of Camel, the interval is not being respected in the first few
exchanges.

Notice at the end of the log how the first QUARTZ log entries are piled
together (interval 1200). If I shorten the interval I can pile them up even
more (3 entries in 100ms with interval 200ms)




...:47,318 INFO  [main] o.q.simpl.SimpleThreadPool - Job execution
threads will use class loader of thread: main
...:47,332 INFO  [main] o.q.core.SchedulerSignalerImpl - Initialized
Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
...:47,333 INFO  [main] o.quartz.core.QuartzScheduler  - Quartz
Scheduler v.2.3.2 created.
...:47,334 INFO  [main] org.quartz.simpl.RAMJobStore   - RAMJobStore
initialized.
...:47,514 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler-camel-1' with
instanceId 'NON_CLUSTERED'
   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
   NOT STARTED.
   Currently in standby mode.
   Number of jobs executed: 0
   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
persistence. and is not clustered.

...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
scheduler 'DefaultQuartzScheduler-camel-1' initialized from an externally
provided properties instance.
...:47,514 INFO  [main] o.q.impl.StdSchedulerFactory   - Quartz
scheduler version: 2.3.2
...:47,545 INFO  [main] o.a.c.c.quartz.QuartzEndpoint  - Job
Camel_camel-1.resolver (triggerType=SimpleTriggerImpl,
jobClass=StatefulCamelJob) is scheduled. Next fire date is Thu Dec 16
19:54:47 WET 2021



...:47,979 INFO  [main] o.a.c.c.quartz.QuartzComponent - Starting
scheduler.
...:47,980 INFO  [main] o.quartz.core.QuartzScheduler  - Scheduler
DefaultQuartzScheduler-camel-1_$_NON_CLUSTERED started.
...:47,993 INFO  [main] o.a.c.c.mock.MockEndpoint  - Asserting:
mock://end is satisfied
...:48,027 INFO  [Worker-1] quartz-daemon  - QUARTZ
...:48,722 INFO  [Worker-2] quartz-daemon

Re: Camel Quartz thread pool

[Claus Ibsen]

Hi

Can you maybe post more details, such as Camel version, and snippets
of your route setup etc. And maybe a bit more about what error happens
that you see that exscapes the thread pool, and maybe point to which
thread pool exactly. This may incline us to help faster and help look
into this.
On Tue, Nov 13, 2018 at 1:59 PM Narapureddy, Santi K
 wrote:
>
> Another Question on top of Camel Threadpools. Is there a way to monitor the 
> routes? This should help to keep a tab on the routes and get a notification 
> when anything happens. We have added onException block on Exception.class. By 
> looking at the thread dump, I can see that the pool is alive. But none of the 
> route is copying the files. So unable to trace what is happening. Any 
> suggestion is highly appreciated.
>
> Thanks
> Santi
>
> On 13/11/18, 4:55 PM, "Narapureddy, Santi K"  
> wrote:
>
> Hi
> I’m having a strange issue where the route is not polling and moving the 
> files at all. Want to understand the Quartz Scheduler’s Thread pool behavior. 
> If I understand correctly when a route is created with a schedule, it created 
> a thread pool with default number of thread (10). BY any chance if there is 
> any RunTimeException occurred in any of the thread, does it kill the whole 
> threadpool and none of the file copy happens after that.
>
> Thanks
> Santi
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.
>
>
>
> This e-mail, including attachments, may include confidential and/or
> proprietary information, and may be used only by the person or entity
> to which it is addressed. If the reader of this e-mail is not the intended
> recipient or his or her authorized agent, the reader is hereby notified
> that any dissemination, distribution or copying of this e-mail is
> prohibited. If you have received this e-mail in error, please notify the
> sender by replying to this message and delete this e-mail immediately.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel Quartz thread pool

[Narapureddy, Santi K]

Another Question on top of Camel Threadpools. Is there a way to monitor the 
routes? This should help to keep a tab on the routes and get a notification 
when anything happens. We have added onException block on Exception.class. By 
looking at the thread dump, I can see that the pool is alive. But none of the 
route is copying the files. So unable to trace what is happening. Any 
suggestion is highly appreciated.

Thanks
Santi

On 13/11/18, 4:55 PM, "Narapureddy, Santi K"  
wrote:

Hi
I’m having a strange issue where the route is not polling and moving the 
files at all. Want to understand the Quartz Scheduler’s Thread pool behavior. 
If I understand correctly when a route is created with a schedule, it created a 
thread pool with default number of thread (10). BY any chance if there is any 
RunTimeException occurred in any of the thread, does it kill the whole 
threadpool and none of the file copy happens after that.

Thanks
Santi

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.



This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Re: camel-quartz failed camel route creation when database is unreachable

[Rachid KRAIEM]

Hello,

Yes, it's my message

Cordialement,

*Rachid KRAIEM*




2016-12-20 17:45 GMT+01:00 Rachid KRAIEM [via Camel] <
ml-node+s465427n5791747...@n5.nabble.com>:

> Hi,
>
> Given the best practice is not to change the APIs, can you raise a JIRA
> that contain this solution and include him in the next release of
> camel-quartz ?
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-
> route-creation-when-database-is-unreachable-tp5789552p5791747.html
> To unsubscribe from camel-quartz failed camel route creation when database
> is unreachable, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-route-creation-when-database-is-unreachable-tp5789552p5791749.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz failed camel route creation when database is unreachable

[Rachid KRAIEM]

Hi,

Given the best practice is not to change the APIs, can you raise a JIRA that
contain this solution and include him in the next release of camel-quartz ?



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-route-creation-when-database-is-unreachable-tp5789552p5791747.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz failed camel route creation when database is unreachable

[Rachid KRAIEM]

Thanks Claus,

Can you raise a JIRA that contain this solution ?



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-route-creation-when-database-is-unreachable-tp5789552p5789852.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz failed camel route creation when database is unreachable

[Claus Ibsen]

Yes there is no re-connection or the likes when starting a quartz route.

You can do as you did with your own custom component.

Its a bit tricky to do re-connection as it would entail a background
thread keep running and trying to startup the route until its
succesful, and then you need ways to configure how often it should
try, and whatnot.

Camel 3.x will introduce async startup of routes and as well a way of
configuring retry strategies etc. that would work generic for all
routes/consumers.


On Tue, Nov 1, 2016 at 11:49 AM, Rachid KRAIEM  wrote:
> Hi Everyone:
>
> My bundle osgi installed into karaf container 4.0.7, that use
> camel-quartz2-2.17.3 In camelContext I have many routes such as "myRoute",
> it call a job quatrz (using camel-quartz2) configured in postgresql
> database:
>
> 
> Camel route
> 
>
>
>   xmlns="http://camel.apache.org/schema/blueprint;>
>
> 
> 
> uri="quartz2://statGroup/startupTimer?cron={{stat.purge.wan.volume.daily.dc}}"
> />
> 
> 
>
>  
>
> 
> Bean quartz2
> 
>
>   class="org.apache.camel.component.quartz2.QuartzComponent">
>  value="file:etc/stat_quartz.cfg" />
>  
>
> 
> quartz2 configuration : stat_quartz.cfg
> 
>
>
> #
> # Configure Main Scheduler Properties
> #
> org.quartz.scheduler.instanceName=Scheduler
> org.quartz.scheduler.instanceId=AUTO
> org.quartz.scheduler.skipUpdateCheck=true
> org.quartz.scheduler.jobFactory.class=org.quartz.simpl.SimpleJobFactory
> #
> # Configure ThreadPool
> #
> org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool
> org.quartz.threadPool.threadCount=10
> #
> # Configure JobStore
> #
> org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX
> org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
> org.quartz.jobStore.dataSource=statQuartzDS
> org.quartz.jobStore.tablePrefix=stat_qrtz_
> org.quartz.jobStore.isClustered=true
> org.quartz.jobStore.clusterCheckinInterval=2
> org.quartz.jobStore.useProperties=false
> #
> # Configure Datasources
> #
> org.quartz.dataSource.statQuartzDS.jndiURL=osgi:service/statQuartzDS
>
>
> 
> Problem
> 
>
>
> My issue is when I try to starting the karaf container and postgresql is
> stopped, I have the log problem below and the camelContext "myCamelContext"
> will be shutdown.
>
>
> 2016-10-14 17:21:40,201 | ERROR | FelixStartLevel  | BlueprintCamelContext
> | 80 - org.apache.camel.camel-blueprint - 2.17.3 | Error occurred during
> starting Camel: CamelContext(statisticsContext) due Failed to create route
> myRoute: Route(myRoute)[[From[quartz2://stat... because of Failed to resolve
> endpoint:
> quartz2://statGroup/startupTimer?trigger.repeatCount=0=1
> due to: Failed to obtain DB connection from data source 'statQuartzDS':
> java.sql.SQLException: Could not retrieve datasource via JNDI url
> 'osgi:service/statQuartzDS' java.sql.SQLException: Unable to acquire a new
> connection from the pool
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> myRoute: Route(myRoute)[[From[quartz2://stat... because of Failed to resolve
> endpoint:
> quartz2://statGroup/startupTimer?trigger.repeatCount=0=1
> due to: Failed to obtain DB connection from data source 'statQuartzDS':
> java.sql.SQLException: Could not retrieve datasource via JNDI url
> 'osgi:service/statQuartzDS' java.sql.SQLException: Unable to acquire a new
> connection from the pool
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:201)
> at
> 

Re: camel-quartz failed camel route creation when database is unreachable

[souciance]

I cannot comment on the code for starting the route when the database is
unavailable but why  not add some default properties to use when the
database is not available. Then you catch the exception and use those
properties instead.



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-route-creation-when-database-is-unreachable-tp5789552p5789827.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz failed camel route creation when database is unreachable

[Rachid KRAIEM]

Hi Everyone,

Can you validate this proposal



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-failed-camel-route-creation-when-database-is-unreachable-tp5789552p5789822.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz memory leak

[Akram]

I have resolved the issue.. It is an issue with quartz component. Quartz was
being shutdown but the webapp didn't wait for quartz to finish before it
shutdown so Tomcat decided that it had left threads running and complained.
So, i override the shutdown method in quartzcomponent as follows and it
worked for me..

@Override
public void shutdown() throws SchedulerException, InterruptedException {
Scheduler scheduler = super.getScheduler();
if (scheduler != null) {
scheduler.shutdown(true);
Thread.sleep(1000);
scheduler = null;
}
}

Note the boolean argument to shutdown is the vital part. If you remove that
true to call the no-arg version or set it to false, your webapp won't wait
for quartz to shudown before it shuts down.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5770634.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz memory leak

[Greg Autric]

Hi Akram,

feel free to rise a JIRA ticket (https://issues.apache.org/jira/browse/CAMEL)
And create an PR to github (https://github.com/apache/camel)

Camel commiters will analyse it, and accept it if it is confirmed issue.

thx for your help,

Greg AUTRIC
JBoss Middleware Consultant

email   : gautric __at__ redhat __dot__ com
twitter : @gautric_io

Red Hat Global Services
Red Hat France SARLsit: http://www.redhat.fr
Le Linea, 1 rue du General Leclerc, 92047 Paris La Défense Cedex
Sent from webmail

- Mail original -
De: Akram akram.s...@gmail.com
À: users@camel.apache.org
Envoyé: Mercredi 12 Août 2015 23:11:41
Objet: Re: Camel quartz memory leak

I have resolved the issue.. It is an issue with quartz component. Quartz was
being shutdown but the webapp didn't wait for quartz to finish before it
shutdown so Tomcat decided that it had left threads running and complained.
So, i override the shutdown method in quartzcomponent as follows and it
worked for me..

@Override
public void shutdown() throws SchedulerException, InterruptedException {
Scheduler scheduler = super.getScheduler();
if (scheduler != null) {
scheduler.shutdown(true);
Thread.sleep(1000);
scheduler = null;
}
}

Note the boolean argument to shutdown is the vital part. If you remove that
true to call the no-arg version or set it to false, your webapp won't wait
for quartz to shudown before it shuts down.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5770634.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz memory leak

[Akram]

I am using camel 2.15.1. Stopping the route using JMX, againg restarting it
using JMX. Also the same getting same error if I restart entire camel
context.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5768275.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz memory leak

[Willem Jiang]

When you stop the route, the schedule won’t be shutdown.
But if you stop the camel context, the schedule will be shutdown if there is no 
CamelJob there.

Are there more than one camel-quartz endpoints in your camel route?

--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem



On June 15, 2015 at 10:36:57 PM, Akram (akram.s...@gmail.com) wrote:
 I am using camel 2.15.1. Stopping the route using JMX, againg restarting it
 using JMX. Also the same getting same error if I restart entire camel
 context.
  
  
  
 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063p5768275.html
   
 Sent from the Camel - Users mailing list archive at Nabble.com.
  

Re: Camel quartz memory leak

[Claus Ibsen]

Hi

What version of Camel do you use? And how do you restart the route?

On Wed, Jun 10, 2015 at 11:33 AM, Akram akram.s...@gmail.com wrote:
 I am using camel quartz to run a job every minute. But whenever i restart the
 quartz route I get the message:

 appears to have started a thread named [MyScheduler_Worker-1] but has failed
 to stop it.This is very likely to create a memory leak. Stack trace of
 thread: java.lang.Object.wait(Native Method)
 org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:543)
 Jun 10, 2015 10:01:03 AM org.apache.catalina.loader.WebappClassLoaderBase
 clearReferencesThreads



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-quartz-memory-leak-tp5768063.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: Camel quartz misfires and route not getting run / triggered after exception:ObjectAlreadyExistsException

[lakshmi.prashant]

Hi,

   Can you kindly explain why the route starts failing after running for
sometime..
   Why is the doAddJob() getting called, after few runs of a schedule have
already tun, as reported in the exception? 
   The race condition can happen only at the start of the route, while
scheduling the quartz job. But it gets reported after few runs in the below
exception trace:

http://camel.465427.n5.nabble.com/file/n5743232/Route_Stoping_After_fewruns.png
 

Thanks,
Lakshmi

Exception Trace:
ERROR#org.apache.camel.blueprint.BlueprintCamelContext##anonymous#Blueprint
Extender: 3##avatarcl#aq4appaq4t#iflmap#null#null#
Error occurred during starting Camel: CamelContext(context4) due 
Unable to store Trigger with name: 'schedule3' and group: 'Camel', because
one already exists with this
identification.org.quartz.ObjectAlreadyExistsException: 
Unable to store Trigger with name: 'schedule3' and group: 'Camel', because
one already exists with this identification. at
org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1200)
 
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1072)
at
org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:3716)
 
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3788)
at org.quartz.impl.jdbcjobstore.JobStoreTX.executeInLock(JobStoreTX.java:90) 
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3712)
 
at
org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigger(JobStoreSupport.java:1059)
at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:822) 
at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243) at
org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
 
at
org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:222)
at
org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:81)
 
at
org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:213)
at
org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39)
 
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) at
org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1819)
 
at
org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:2113)
 
at
org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:2049)
 
at
org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:1979)
 
at
org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:1758)
 
at
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1633)
 
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1500)
 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-misfires-and-route-not-getting-run-triggered-after-exception-ObjectAlreadyExistsExceptin-tp5739997p5743232.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz misfires and route not getting run / triggered after exception:ObjectAlreadyExistsException

[Babak Vahdat]

Hi

As you've already reported by your first post, only increasing the number of
running VM's makes this exception to happen (from 2 to 7). This CAN be a
hint for a race-condition somewhere. There was a similar problem being
reported while ago:

https://issues.apache.org/jira/browse/CAMEL-6686

The only reason why we could fix that was because we could reproduce the
same exception inside a test, which is now added to the code base of this
Camel module. In your case I was NOT able to do the same. If you could
somehow provide a test or a sample project then we could dig into this to
see if we can find the root cause of the problem and probably fix it.
There's also the following Camel test module you could make use of for this:

http://camel.apache.org/blueprint-testing.html

Babak


lakshmi.prashant wrote
 Hi,
 
Can you kindly explain why the route starts failing after running for
 sometime..
Why is the doAddJob() getting called, after few runs of a schedule have
 already tun, as reported in the exception? 
The race condition can happen only at the start of the route, while
 scheduling the quartz job. But it gets reported after few runs in the
 below exception trace:
http://camel.465427.n5.nabble.com/file/n5743232/Route_Stoping_After_fewruns.png
 
 
 Thanks,
 Lakshmi
 
 Exception Trace:
 ERROR#org.apache.camel.blueprint.BlueprintCamelContext##anonymous#Blueprint
 Extender: 3##avatarcl#aq4appaq4t#iflmap#null#null#
 Error occurred during starting Camel: CamelContext(context4) due 
 Unable to store Trigger with name: 'schedule3' and group: 'Camel', because
 one already exists with this
 identification.org.quartz.ObjectAlreadyExistsException: 
 Unable to store Trigger with name: 'schedule3' and group: 'Camel', because
 one already exists with this identification. at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1200)
  
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1072)
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:3716)
  
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3788)
 at
 org.quartz.impl.jdbcjobstore.JobStoreTX.executeInLock(JobStoreTX.java:90) 
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3712)
  
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigger(JobStoreSupport.java:1059)
 at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:822) 
 at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243) at
 org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
  
 at
 org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:222)
 at
 org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:81)
  
 at
 org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:213)
 at
 org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39)
  
 at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
 at
 org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1819)
  
 at
 org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:2113)
  
 at
 org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:2049)
  
 at
 org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:1979)
  
 at
 org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:1758)
  
 at
 org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1633)
  
 at
 org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1500)





--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-misfires-and-route-not-getting-run-triggered-after-exception-ObjectAlreadyExistsExceptin-tp5739997p5743238.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz misfires and route not getting run / triggered after exception:ObjectAlreadyExistsException

[Babak Vahdat]

Hi

Thanks for getting back. Your Quartz configuration seems fine.

To me this sounds like a bug in Quartz itself as Quartz claims that the
trigger is null/non-existing but when we try to schedule the Job using that
given trigger it blows up with ObjectAlreadyExistsException.

That said there's a race condition between the time window as we ask for a
pre-existing trigger and the point where we try to schedule the Job. What if
in this time window another JVM (a cluster member) schedules a Job using the
same trigger name/group. IMHO what actually would come handy here would be a
*atomic* Quartz-API for this, something like what we already have in Java
itself:

http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ConcurrentHashMap.html#putIfAbsent(K,%20V)

Which as it's Javadoc already says is equivalent to:

if (!map.containsKey(key))
   return map.put(key, value);
else
   return map.get(key);

Except that the action is performed *atomically*.

Maybe you want to ask for help using the Quartz user-forum itself and refer
to this thread?

Babak


lakshmi.prashant wrote
 Hi,
 
   Sorry for the delay in response. I did not get notified in my mail box
 and hence had not followed your reply to the mail thread.
 
 Please find below my answers and the blueprint xml used in the cluster
 with 7 VM's.
 
 Thanks,
 Lakshmi
 

  - Which exact Quartz 1.x version do you make use of? : 
/
 Ans: I am using servicemix quartz 1.8.6_1 bundle.
/
 
 - Can you reproduce this with the latest Camel 2.12.1 version? 
/
 Ans: Yes. It happens in big clusters. Has any fix been provided with camel
 2.12.1?
/
 
 - And CAMEL-5994 is already fixed so this should not cause any problem for
 you 
 - Also looking at the stacktrace I think Quartz has not been setup
 properly in Cluster-Mode (see
 org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
 on the call-stack)... Did you set the org.quartz.jobStore.isClustered and
 org.quartz.jobStore.clusterCheckinInterval properties appropriately?
/
 Ans: Please find the blueprint XML that I had used. I have set isClustered
 as true and the logs showed that the route got triggered by quartz in
 different cluster VM's for different runs, till the exception got
 reported. But I was not sure of the right value for the checkin interval
 in the cluster and had not specified any specific value.
/
 
  - As you run inside OSGi but assign the id of 
 camelContext
  by yourself (e.g. context4), have you seen the blue-box about this here
 http://camel.apache.org/quartz
/
 Ans: I am assigning an unique id for each bundle with the camel route. As
 of now, I had tested with only 1 bundle deployed in multiple cluster nodes
  hence I guess that the context id should not be a problem.
 
 I will also check by removing the context id, as well.
/
 
 
 I  had a look at the quartz component source code: The error trace shows
 that existingTrigger is null. It looks like that a race condition is
 occuring between the different VM's. Both of them are likely getting the
 trigger name as null and try to schedule the job..but the job is already
 scheduled
 
   private void doAddJob(JobDetail job, Trigger trigger) throws
 SchedulerException {
 incrementJobCounter(getScheduler());
 
 Trigger existingTrigger =
 getScheduler().getTrigger(trigger.getName(), trigger.getGroup());
 if (existingTrigger == null) {
 LOG.debug(Adding job using trigger: {}/{},
 trigger.getGroup(), trigger.getName());
 
*
 getScheduler().scheduleJob(job, trigger);
*
 } else if (hasTriggerChanged(existingTrigger, trigger)) {
 LOG.debug(Trigger: {}/{} already exists and will be updated
 by Quartz., trigger.getGroup(), trigger.getName());
 // fast forward start time to now, as we do not want any
 misfire to kick in
 trigger.setStartTime(new Date());
 // replace job, and relate trigger to previous job name, which
 is needed to reschedule job
 scheduler.addJob(job, true);
 trigger.setJobName(existingTrigger.getJobName());
 scheduler.rescheduleJob(trigger.getName(), trigger.getGroup(),
 trigger);
 } else {
 if (!isClustered()) {
 LOG.debug(Trigger: {}/{} already exists and will be
 resumed by Quartz., trigger.getGroup(), trigger.getName());
 // fast forward start time to now, as we do not want any
 misfire to kick in
 trigger.setStartTime(new Date());
 // replace job, and relate trigger to previous job name,
 which is needed to reschedule job
 scheduler.addJob(job, true);
 trigger.setJobName(existingTrigger.getJobName());
 scheduler.rescheduleJob(trigger.getName(),
 trigger.getGroup(), trigger);
 } else {
 LOG.debug(Trigger: {}/{} already exists and is already
 scheduled by clustered JobStore., trigger.getGroup(), 

Re: Camel quartz misfires and route not getting run / triggered after exception:ObjectAlreadyExistsException

[lakshmi.prashant]

Hi,

  Sorry for the delay in response. I did not get notified in my mail box and
hence had not followed your reply to the mail thread.

Please find below my answers and the blueprint xml used in the cluster with
7 VM's.

Thanks,
Lakshmi

   
 - Which exact Quartz 1.x version do you make use of? : 
/Ans: I am using servicemix quartz 1.8.6_1 bundle./

- Can you reproduce this with the latest Camel 2.12.1 version? 
/Ans: Yes. It happens in big clusters. Has any fix been provided with camel
2.12.1?/

- And CAMEL-5994 is already fixed so this should not cause any problem for
you 
- Also looking at the stacktrace I think Quartz has not been setup properly
in Cluster-Mode (see
org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
on the call-stack)... Did you set the org.quartz.jobStore.isClustered and
org.quartz.jobStore.clusterCheckinInterval properties appropriately?
/Ans: Please find the blueprint XML that I had used. I have set isClustered
as true and the logs showed that the route got triggered by quartz in
different cluster VM's for different runs, till the exception got reported.
But I was not sure of the right value for the checkin interval in the
cluster and had not specified any specific value./

 - As you run inside OSGi but assign the id of camelContext by yourself
(e.g. context4), have you seen the blue-box about this here
http://camel.apache.org/quartz

/Ans: I am assigning an unique id for each bundle with the camel route. As
of now, I had tested with only 1 bundle deployed in multiple cluster nodes 
hence I guess that the context id should not be a problem.

I will also check by removing the context id, as well.
/


I  had a look at the quartz component source code: The error trace shows
that existingTrigger is null. It looks like that a race condition is
occuring between the different VM's. Both of them are likely getting the
trigger name as null and try to schedule the job..but the job is already
scheduled

  private void doAddJob(JobDetail job, Trigger trigger) throws
SchedulerException {
incrementJobCounter(getScheduler());

Trigger existingTrigger =
getScheduler().getTrigger(trigger.getName(), trigger.getGroup());
if (existingTrigger == null) {
LOG.debug(Adding job using trigger: {}/{}, trigger.getGroup(),
trigger.getName());
*getScheduler().scheduleJob(job, trigger);*
} else if (hasTriggerChanged(existingTrigger, trigger)) {
LOG.debug(Trigger: {}/{} already exists and will be updated by
Quartz., trigger.getGroup(), trigger.getName());
// fast forward start time to now, as we do not want any misfire
to kick in
trigger.setStartTime(new Date());
// replace job, and relate trigger to previous job name, which
is needed to reschedule job
scheduler.addJob(job, true);
trigger.setJobName(existingTrigger.getJobName());
scheduler.rescheduleJob(trigger.getName(), trigger.getGroup(),
trigger);
} else {
if (!isClustered()) {
LOG.debug(Trigger: {}/{} already exists and will be resumed
by Quartz., trigger.getGroup(), trigger.getName());
// fast forward start time to now, as we do not want any
misfire to kick in
trigger.setStartTime(new Date());
// replace job, and relate trigger to previous job name,
which is needed to reschedule job
scheduler.addJob(job, true);
trigger.setJobName(existingTrigger.getJobName());
scheduler.rescheduleJob(trigger.getName(),
trigger.getGroup(), trigger);
} else {
LOG.debug(Trigger: {}/{} already exists and is already
scheduled by clustered JobStore., trigger.getGroup(), trigger.getName());
}
}
}




*Blueprint XML used by me:*


?xml version=1.0 encoding=UTF-8?
blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;

xmlns:Generator=com.sap.it.gnb.ifl.common.gen.pluggability.api.GeneratorHandler
xmlns:str=http://exslt.org/strings; 
xmlns:exsl=http://exslt.org/common;
xmlns:ext=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:idocsoap=urn:sap-com:document:sap:idoc:soap:messages
xmlns:bsn=http://sapcd.com/bsnagt;
xmlns:ns=https://bsnschemas.netweaver.neo.com/bsnflow;
xmlns:jaxws=http://cxf.apache.org/blueprint/jaxws;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:sec=http://cxf.apache.org/configuration/security;
xmlns:wsrm-policy=http://schemas.xmlsoap.org/ws/2005/02/rm/policy;
xmlns:wsrm-mgr=http://cxf.apache.org/ws/rm/manager;
xmlns:wsa=http://cxf.apache.org/ws/addressing;
xmlns:http-conf=http://cxf.apache.org/transports/http/configuration;
xmlns:cxfcore=http://cxf.apache.org/blueprint/core;

Re: Camel quartz misfires and route not getting run / triggered after exception:ObjectAlreadyExistsException

[Babak Vahdat]

Hi

Were you able to find the root cause of the problem here? If not:

- Which exact Quartz 1.x version do you make use of?
- Can you reproduce this with the latest Camel 2.12.1 version?
- And CAMEL-5994 is already fixed so this should not cause any problem for
you
- Also looking at the stacktrace I think Quartz has not been setup properly
in Cluster-Mode (see
org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
on the call-stack)... Did you set the org.quartz.jobStore.isClustered and
org.quartz.jobStore.clusterCheckinInterval properties appropriately?
- As you run inside OSGi but assign the id of camelContext by yourself
(e.g. context4), have you seen the blue-box about this here
http://camel.apache.org/quartz

Babak


lakshmi.prashant wrote
 Hi,
 
   I am running camel quartz (2.10.4)  quartz has been set-up in clustered
 mode. The clocks in the cluster are synchronized.
 
   I have set-up a trigger to run every 1 minute, via the camel-quartz
 end-point in my route.
 
   a) it works fine if quartz is not set up in clustered mode (uses
 RAMJobstore).
 
   b) If quartz is set up in clustred mode, it was working fine when there
 were only 2 nodes in the cluster.
   Sometimes, instead of every 1 minute, the runs used to get fired
 every 2 minutes over a time-window, but it seemed to stabilize and run
 fine.
 
   c) After I increased the number of VM's in the cluster (to ~7 VM's), I
 faced misfires..
  
  i) The routes used to be triggered correctly for sometime and then
 stop working altogether..
  ii) The below exception has been logged in 1 (or) more VM's in the
 cluster, after which  the camel endpoints seemed to not fire at all. PFA
 the depiction of misfires from camel.
 
 Note: This issue is noticed in 2.11 camel as well. Is this related to
 https://issues.apache.org/jira/browse/CAMEL-5994... And has this not been
 fixed till now?
 
 Kindly help.
 
 Thanks,
 Lakshmi
 
 Exception Trace:
 
 ERROR#org.apache.camel.blueprint.BlueprintCamelContext##anonymous#Blueprint
 Extender: 3##avatarcl#aq4appaq4t#iflmap#null#null#Error occurred during
 starting Camel: CamelContext(context4) due Unable to store Trigger with
 name: 'schedule3' and group: 'Camel', because one already exists with this
 identification.org.quartz.ObjectAlreadyExistsException: Unable to store
 Trigger with name: 'schedule3' and group: 'Camel', because one already
 exists with this identification.
 at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1200)
   at
 org.quartz.impl.jdbcjobstore.JobStoreSupport$3.execute(JobStoreSupport.java:1072)
   at
 org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:3716)
   at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3788)
   at
 org.quartz.impl.jdbcjobstore.JobStoreTX.executeInLock(JobStoreTX.java:90)
   at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3712)
   at
 org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigger(JobStoreSupport.java:1059)
   at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:822)
   at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243)
   at
 org.apache.camel.component.quartz.QuartzComponent.doAddJob(QuartzComponent.java:232)
   at
 org.apache.camel.component.quartz.QuartzComponent.addJob(QuartzComponent.java:222)
   at
 org.apache.camel.component.quartz.QuartzEndpoint.addTrigger(QuartzEndpoint.java:81)
   at
 org.apache.camel.component.quartz.QuartzEndpoint.consumerStarted(QuartzEndpoint.java:213)
   at
 org.apache.camel.component.quartz.QuartzConsumer.doStart(QuartzConsumer.java:39)
   at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
   at
 org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:1819)
   at
 org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRouteConsumers(DefaultCamelContext.java:2113)
   at
 org.apache.camel.impl.DefaultCamelContext.doStartRouteConsumers(DefaultCamelContext.java:2049)
   at
 org.apache.camel.impl.DefaultCamelContext.safelyStartRouteServices(DefaultCamelContext.java:1979)
   at
 org.apache.camel.impl.DefaultCamelContext.doStartOrResumeRoutes(DefaultCamelContext.java:1758)
   at
 org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1633)
   at
 org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1500)
 
   
http://camel.465427.n5.nabble.com/file/n5739997/FailedRuns.jpg 
http://camel.465427.n5.nabble.com/file/n5739997/runs_successful_with_2_VMs.jpg
 
http://camel.465427.n5.nabble.com/file/n5739997/some_runs_misfiring_fire_in_2_mins.jpg
 




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-misfires-and-route-not-getting-run-triggered-after-exception-ObjectAlreadyExistsExceptin-tp5739997p5740345.html
Sent 

Re: Camel Quartz Query

[Taariq Levack]

Hi

Can you use an idempotent consumer[1] before sending to the web service?
http://camel.apache.org/idempotent-consumer.html

If you did have a sort of 'busy' status, you'd have to handle the situation
where records are left in that 'busy' state due to a JVM crash for example.

Taariq


On Wed, Sep 25, 2013 at 5:20 PM, gilboy josephoto...@gmail.com wrote:

 Hi

 I have a quartz job(stateful) which wakes up every 60 seconds, pulls
 unprocessed records from a DB and sends each of them to a Web Service
 Endpoint. The Web Service call introduces a latency of approx .5 sec. Each
 time the quartz job fires there can be 100's of unprocessed records.
 Hence, after retrieving the records I iterate over the records via the
 splitter and I load balance(sticky - need to maintain order across subsets
 of the records) to 10 different seda queues. I then have 10 different
 routes
 which takes from each of the queues, transmits the message to the web
 service endpoint and then updates the record to be in a processed state.

 However, with the above approach I could easily send duplicates to the web
 service endpoint because a record which is returned when the quartz job
 fires at time 0 could be sitting on one of the seda queues at time 60 when
 the quartz job fires again and hence it is still in an unprocessed state
 in the database as it only gets updated to processed when we get a
 response from the Web Service call.

 I could solve this by introducing a new interim status and have the DB
 update the unprocessed records to the new interim status but just wanted
 to check to see if there was any other way of solving this as I have less
 control over the DB

 Thanks
 Joe



 --
 View this message in context:
 http://camel.465427.n5.nabble.com/Camel-Quartz-Query-tp5740206.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz Query

[Christian Posta]

+1 idempotent consumer. that should work nicely.


On Wed, Sep 25, 2013 at 10:59 PM, Taariq Levack taar...@gmail.com wrote:

 Hi

 Can you use an idempotent consumer[1] before sending to the web service?
 http://camel.apache.org/idempotent-consumer.html

 If you did have a sort of 'busy' status, you'd have to handle the situation
 where records are left in that 'busy' state due to a JVM crash for example.

 Taariq


 On Wed, Sep 25, 2013 at 5:20 PM, gilboy josephoto...@gmail.com wrote:

  Hi
 
  I have a quartz job(stateful) which wakes up every 60 seconds, pulls
  unprocessed records from a DB and sends each of them to a Web Service
  Endpoint. The Web Service call introduces a latency of approx .5 sec.
 Each
  time the quartz job fires there can be 100's of unprocessed records.
  Hence, after retrieving the records I iterate over the records via the
  splitter and I load balance(sticky - need to maintain order across
 subsets
  of the records) to 10 different seda queues. I then have 10 different
  routes
  which takes from each of the queues, transmits the message to the web
  service endpoint and then updates the record to be in a processed
 state.
 
  However, with the above approach I could easily send duplicates to the
 web
  service endpoint because a record which is returned when the quartz job
  fires at time 0 could be sitting on one of the seda queues at time 60
 when
  the quartz job fires again and hence it is still in an unprocessed
 state
  in the database as it only gets updated to processed when we get a
  response from the Web Service call.
 
  I could solve this by introducing a new interim status and have the DB
  update the unprocessed records to the new interim status but just
 wanted
  to check to see if there was any other way of solving this as I have less
  control over the DB
 
  Thanks
  Joe
 
 
 
  --
  View this message in context:
  http://camel.465427.n5.nabble.com/Camel-Quartz-Query-tp5740206.html
  Sent from the Camel - Users mailing list archive at Nabble.com.
 




-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Re: camel-quartz and support for quartz 2.x

[Claus Ibsen]

Camel 2.12 will include a camel-quartz2 component
http://camel.apache.org/quartz2

On Mon, Aug 12, 2013 at 9:14 AM, ravishankar.singaram
bytes2r...@gmail.com wrote:
 Hi Patrick,

 Did you find any luck in implementing Quartz 2.x for Camel?

 Note: We are trying to employ Quartz for enabling multi-node clustering for
 our camel routes. There was some issues while using the default Quartz
 version, we felt should upgrade to the latest Quartz version.



 -
 Ravishankar Singaram
 Technical Lead
 Amadeus Software Labs
 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5737113.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: camel-quartz and support for quartz 2.x

[Claus Ibsen]

No Camel 2.11 will NOT support Quartz 2.x. One of the reason is Spring
3.0.x does not support Quartz 2.x, and Camel 2.11 is spring 3.0
compatible.

Camel 2.12 will be updated to Quartz 2.x as we dropped support for
Spring 3.0 in this release.

For Camel 2.11 you may manually try to upgrade quartz to 2.x if you
are not using spring or using spring 3.1 or better. Though not sure if
you hit any issue in doing so.

On Thu, May 30, 2013 at 7:36 AM, Patrick Bray patrick.b...@gmail.com wrote:
 Hi All,

 Can you please confirm whether or not Camel v2.11.0 supports Quartz v2.x?

 Checking JIRA I can see the following ticket is unresolved:

 https://issues.apache.org/jira/browse/CAMEL-4075

 If not can you adivse whether or not this is on the road map for Camel
 2.11.1?

 The issue we have is that we intend to have multiple application components
 deployed that utilise a Clustered Quartz JDBC job store.

 From what I understand Quartz 1.8.x does not allow multiple logical
 schedulers to share the same job store where as 2.x does (see
 http://forums.terracotta.org/forums/posts/list/5562.page).

 Thanks,
 Patrick Bray



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5733444.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
www.camelone.org: The open source integration conference.

Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

RE: camel-quartz and support for quartz 2.x

[Bray, Patrick]

Ok excellent thanks for the clarification Claus as we are using Spring
v3.1.3 I will try manually updating and post back with my results.

-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com] 
Sent: Thursday, 30 May 2013 3:40 PM
To: users@camel.apache.org
Subject: Re: camel-quartz and support for quartz 2.x

No Camel 2.11 will NOT support Quartz 2.x. One of the reason is Spring
3.0.x does not support Quartz 2.x, and Camel 2.11 is spring 3.0
compatible.

Camel 2.12 will be updated to Quartz 2.x as we dropped support for
Spring 3.0 in this release.

For Camel 2.11 you may manually try to upgrade quartz to 2.x if you are
not using spring or using spring 3.1 or better. Though not sure if you
hit any issue in doing so.

On Thu, May 30, 2013 at 7:36 AM, Patrick Bray patrick.b...@gmail.com
wrote:
 Hi All,

 Can you please confirm whether or not Camel v2.11.0 supports Quartz
v2.x?

 Checking JIRA I can see the following ticket is unresolved:

 https://issues.apache.org/jira/browse/CAMEL-4075

 If not can you adivse whether or not this is on the road map for Camel

 2.11.1?

 The issue we have is that we intend to have multiple application 
 components deployed that utilise a Clustered Quartz JDBC job store.

 From what I understand Quartz 1.8.x does not allow multiple logical 
 schedulers to share the same job store where as 2.x does (see 
 http://forums.terracotta.org/forums/posts/list/5562.page).

 Thanks,
 Patrick Bray



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-
 2-x-tp5712613p5733444.html Sent from the Camel - Users mailing list 
 archive at Nabble.com.



--
Claus Ibsen
-
www.camelone.org: The open source integration conference.

Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
This e-mail and any attachments to it (the Communication) is, unless 
otherwise stated, confidential,  may contain copyright material and is for the 
use only of the intended recipient. If you receive the Communication in error, 
please notify the sender immediately by return e-mail, delete the Communication 
and the return e-mail, and do not read, copy, retransmit or otherwise deal with 
it. Any views expressed in the Communication are those of the individual sender 
only, unless expressly stated to be those of Australia and New Zealand Banking 
Group Limited ABN 11 005 357 522, or any of its related entities including ANZ 
Bank New Zealand Limited (together ANZ). ANZ does not accept liability in 
connection with the integrity of or errors in the Communication, computer 
virus, data corruption, interference or delay arising from or in respect of the 
Communication.

Re: Camel Quartz and JobStore

[garrydias]

JBoss 7 does not have Quartz in its modules.

Is this problem related to this issue
https://issues.apache.org/jira/browse/CAMEL-6067?

thanx



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5733043.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[garrydias]

Hi mpaiva.

The jboss 7 disable feature is not directly related to your issue. It seems
your jboss7 disable procedure is shutting down your CamelContext and your
quartz routes as well.

Can u certify yourself if the tables data disapears at CamelContext
shutdown?

[]s



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5732971.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[Chris Wolf]

Don't forget that JBoss runs it's own instance of Quartz as a service.
I'm not sure
how you're configuring the JobStore implementation, but if it's via
the quartz.properties
and the JBoss instance of quartz reads the same properties, then maybe
there's a conflict?

On Mon, May 20, 2013 at 5:41 PM, mpaivafontes mpaivafon...@gmail.com wrote:
 Hello,

 I'm trying to use the misfire property from Camel-Quartz persisting the data
 at the database ( SQL server ) with JobStore from Quartz but i'm facing a
 strange problem after the restart of the application.

 For some reason after the restart, all data disappear for some reason and
 the misfire is not getting triggered.

 When i setted the xx.isClustered=true the all data is kept what does make
 sense, but it's not my case.

 I would like to know if is there any way to keep the data intact after the
 app restart so i can see the misfire working properly.

 The class used to control the transaction is
 org.quartz.impl.jdbcjobstore.JobStoreTX

 Regards !



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[mpaivafontes]

Hello garrydias,

The data disapear during the CamelContext shutdown at the route shutdown.

*14:43:19,421 INFO  [org.apache.camel.spring.SpringCamelContext] (MSC
service thread 1-7) Apache Camel 2.11.0 (CamelContext:
infosender-scheduler-camelContext) is shutting down*
14:43:19,423 INFO  [org.apache.camel.impl.DefaultShutdownStrategy] (MSC
service thread 1-7) Starting to graceful shutdown 71 routes (timeout 300
seconds)
14:43:19,444 INFO  [org.apache.camel.impl.DefaultShutdownStrategy] (Camel
(infosender-scheduler-camelContext) thread #25 - ShutdownTask) Route:
/schedule540 shutdown complete, was consuming from:
Endpoint[quartz://?cron=0+0+12%2C17+*+*+%3Fstateful=truetrigger.misfireInstruction=1]
.
.
.
14:43:20,007 INFO  [org.apache.camel.impl.DefaultShutdownStrategy] (MSC
service thread 1-7) Graceful shutdown of 71 routes completed in 0 seconds
14:43:20,860 INFO  [org.apache.camel.component.quartz.QuartzComponent] (MSC
service thread 1-7) There are no more jobs registered, so shutting down
Quartz scheduler: QuartzScheduler
14:43:20,865 INFO  [org.quartz.core.QuartzScheduler] (MSC service thread
1-7) Scheduler QuartzScheduler_$_NON_CLUSTERED shutting down.
14:43:20,866 INFO  [org.quartz.core.QuartzScheduler] (MSC service thread
1-7) Scheduler QuartzScheduler_$_NON_CLUSTERED paused.
14:43:20,867 INFO  [org.quartz.core.QuartzScheduler] (MSC service thread
1-7) Scheduler QuartzScheduler_$_NON_CLUSTERED shutdown complete.
14:43:20,878 INFO  [org.apache.camel.spring.SpringCamelContext] (MSC service
thread 1-7) Uptime 28.908 seconds
*14:43:20,879 INFO  [org.apache.camel.spring.SpringCamelContext] (MSC
service thread 1-7) Apache Camel 2.11.0 (CamelContext:
infosender-scheduler-camelContext) is shutdown in 1.457 seconds*



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5732978.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[mpaivafontes]

Hello Chris Wolf,

I don't think it could be a conflict problem since that the properties are
been set correctly 
Anyway i'm going to check

Thanks for reply



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5732982.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[mpaivafontes]

Hello Claus,

I'm already setting stateful=true and the data is getting modified properly.

I've noticed that the  IS_VOLATILE column might have something in this, but
i've changed by updating the column manually but nothing happened.

I'm using jboss7.1 and when i disable the app the data get deleted after
each route shutdown.

Any other idea what might be ?

Thanks



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5732897.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz and JobStore

[Claus Ibsen]

Hi

Can you try setting stateful=true


On Mon, May 20, 2013 at 11:41 PM, mpaivafontes mpaivafon...@gmail.com wrote:
 Hello,

 I'm trying to use the misfire property from Camel-Quartz persisting the data
 at the database ( SQL server ) with JobStore from Quartz but i'm facing a
 strange problem after the restart of the application.

 For some reason after the restart, all data disappear for some reason and
 the misfire is not getting triggered.

 When i setted the xx.isClustered=true the all data is kept what does make
 sense, but it's not my case.

 I would like to know if is there any way to keep the data intact after the
 app restart so i can see the misfire working properly.

 The class used to control the transaction is
 org.quartz.impl.jdbcjobstore.JobStoreTX

 Regards !



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
www.camelone.org: The open source integration conference.

Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel quartz component query

[cheekychops]

I expect that if you configured quartz to use a clustered jobstore, and
connected to the same database with another quartz instance you could add
more triggers, but I don't think the Quartz Component was really designed to
work this way.

Note that its not recommended to insert triggers directly into the database,
you should use the Quartz API.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-quartz-component-query-tp5728942p5729086.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel quartz component query

[Willem jiang]

Hi,

Camel has the management API[1], which could be used to start or stop the route.
I think you can leverage this API to start a route from the trigger.

[1]http://camel.apache.org/management-example.html  

--  
Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) 
(English)
  http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem





On Tuesday, March 12, 2013 at 12:15 AM, gilboy wrote:

 Hi
  
 Assume I have a route which is using the quartz component(using the quartz
 database store).  
  
 Is it possible at runtime to add new triggers. In other words, assume I have
 an ad-hoc route that I want to execute. If I configure this route to use the
 quartz component with the quartz database store. Can I now add ad-hoc new
 triggers to the database at runtime which will result in the route getting
 executed
  
 Thanks
 Joe
  
  
  
 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-quartz-component-query-tp5728942.html
 Sent from the Camel - Users mailing list archive at Nabble.com 
 (http://Nabble.com).

Re: Camel Quartz Bug

[Christian Müller]

Can you increase the max. cache size for Camel endpoints as described at
[1]?

[1]
http://camel.apache.org/how-do-i-configure-the-maximum-endpoint-cache-size-for-camelcontext.html

Best,
Christian

On Sat, Jan 26, 2013 at 12:11 PM, garrydias garryd...@gmail.com wrote:

 Adding an output of my test case:
 Triggered Jobs: 1200
 Fired Jobs: 200
 camel-quartz-test.txt
 http://camel.465427.n5.nabble.com/file/n5726337/camel-quartz-test.txt



 --
 View this message in context:
 http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726337.html
 Sent from the Camel - Users mailing list archive at Nabble.com.




--

Re: Camel Quartz Bug

[garrydias]

Thanx Christian. You are right. Set Exchange.MAXIMUM_ENDPOINT_CACHE_SIZE
property before camel1.start() is the key to solve my problem.

This is not a bug after all.

Thanx again

[]s




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726392.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz Bug

[Claus Ibsen]

On Mon, Jan 28, 2013 at 12:46 AM, garrydias garryd...@gmail.com wrote:
 Thanx Christian. You are right. Set Exchange.MAXIMUM_ENDPOINT_CACHE_SIZE
 property before camel1.start() is the key to solve my problem.

 This is not a bug after all.


Ah well in fact we fixed an issue in the upcoming Camel releases
related to this, hitting the cache limit.
This should be fixed in next releases of Camel.


 Thanx again

 []s




 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726392.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel Quartz Bug

[Claus Ibsen]

On Fri, Jan 25, 2013 at 8:55 PM, garrydias garryd...@gmail.com wrote:
 ... a little more info:

 When I start 999 camel quartz routes I have 999 triggers fired .

 Is 999 the limit. Why? There´s some extra configuration of something?


Hi

I think you should look at the Quartz Scheduler if there is a
reasonable limit, what a scheduler
can handle of statelful jobs/triggers.

Also you should possible consider your design, why do you need 1000s+
Camel routes that trigger almost
the same quartz cron trigger?


 Thanx



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726288.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel Quartz Bug

[Claus Ibsen]

On Sat, Jan 26, 2013 at 9:37 AM, Claus Ibsen claus.ib...@gmail.com wrote:
 On Fri, Jan 25, 2013 at 8:55 PM, garrydias garryd...@gmail.com wrote:
 ... a little more info:

 When I start 999 camel quartz routes I have 999 triggers fired .

 Is 999 the limit. Why? There´s some extra configuration of something?


 Hi

 I think you should look at the Quartz Scheduler if there is a
 reasonable limit, what a scheduler
 can handle of statelful jobs/triggers.

 Also you should possible consider your design, why do you need 1000s+
 Camel routes that trigger almost
 the same quartz cron trigger?


Oh and you may want to add more threads to the quartz scheduler so it
has more power
as you trigger the jobs at the same time.

You can configure this in the quartz.properties file for example.



 Thanx



 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726288.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



 --
 Claus Ibsen
 -
 Red Hat, Inc.
 FuseSource is now part of Red Hat
 Email: cib...@redhat.com
 Web: http://fusesource.com
 Twitter: davsclaus
 Blog: http://davsclaus.com
 Author of Camel in Action: http://www.manning.com/ibsen



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Re: Camel Quartz Bug

[garrydias]

Thanks Claus.

I redesigned my scheduler project to solve my problem but is a matter of
time until my application start more than 1000 again.

I couldn´t find nothing related to reasonable stateful job limit in the
Quartz docs. Using plain quartz this problem does not happens. Using plain
Quartz I could also fire over 5000 jobs facing a slow down at the job
execution(expected behavior of StatefulJob) only.

And change the threadCount to a different than 10 (default defined by
camel-quarz), the problem still reamains. Camel logs the output bellow,
indicating that 100 threads are started but it is unable to fire more than
1000 jobs.

/279 [main] INFO org.apache.camel.impl.DefaultCamelContext - Apache Camel
2.9.2 (CamelContext: camel-1) is starting
280 [main] INFO org.apache.camel.management.ManagementStrategyFactory - JMX
enabled. Using ManagedManagementStrategy.
416 [main] INFO
org.apache.camel.management.DefaultManagementLifecycleStrategy -
StatisticsLevel at All so enabling load performance statistics
502 [main] INFO
org.apache.camel.impl.converter.AnnotationTypeConverterLoader - Found 3
packages with 15 @Converter classes to load
522 [main] INFO org.apache.camel.impl.converter.DefaultTypeConverter -
Loaded 170 core type converters (total 170 type converters)
526 [main] INFO
org.apache.camel.impl.converter.AnnotationTypeConverterLoader - Loaded 2
@Converter classes
532 [main] INFO org.apache.camel.impl.converter.DefaultTypeConverter -
Loaded additional 9 type converters (total 179 type converters) in 0.009
seconds
544 [main] INFO org.apache.camel.component.quartz.QuartzComponent - Loading
Quartz properties file from classpath: quartz.properties
592 [main] INFO org.quartz.core.SchedulerSignalerImpl - Initialized
Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
592 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.1.8.5
created.
594 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized.
594 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data:
Quartz Scheduler (v1.8.5) 'QuartzScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 100 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support
persistence. and is not clustered.

594 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler
'QuartzScheduler' initialized from an externally provided properties
instance.
594 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler
version: 1.8.5/


The worse case of this fail I see starting 1200 jobs: camel-quartz always
fire only 200 of these jobs. Doesn´t matter the thread pool size .

Thanks again.

Nice weekend



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726336.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel - Quartz hangs on POST calls

[Christian Müller]

You posted the question twice. Please find my answer in [1].

[1]
http://camel.465427.n5.nabble.com/Camel-causes-socket-write-error-td5724284.html

Best,
Christian

On Tue, Dec 18, 2012 at 2:39 PM, krishna krishnab...@gmail.com wrote:

 Hi,

 The quartz-camel set up hangs, if the POST restlet is not returning any
 response.

 Scenario : We have a quartz configured to run every minute which triggers a
 GET restful webservice to get records based on a condition, which is parsed
 and posted to a POST/PUT restful web service.

 Problem : 1. If we are not getting any response from webservice, the camel
 -
 quartz setup is entirely hanging
 2. In some cases, in camel log the message says the URL has been posted,
 but
 I am not able to see the request on the Jetty server log.

 In either of teh scenario, the camel - quartz hangs.

 Please find the camel context below.

 camel.xml http://camel.465427.n5.nabble.com/file/n5724282/camel.xml

 Question:

 How to configure thread time out intreval in camel context for restlet
 calls?

 Environment:

 Camel - 2.8
 JDK - 1.6
 Camel-Quartz - 2.8
 Jetty Server - 7.4.5

 Thanks,
 Krishnan



 --
 View this message in context:
 http://camel.465427.n5.nabble.com/Camel-Quartz-hangs-on-POST-calls-tp5724282.html
 Sent from the Camel - Users mailing list archive at Nabble.com.




--

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

can you tell me how to stop camel routes please. Its urgent to me.


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716245.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

Hi

   Thanks for your quick response... 
and
1.) can u tell me how to stop camel route after it hit the FTP server.
one more thing is
2.) how can i find out the size of files in FTP server?


Thanks and regards..


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716260.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

SimpleTrigger means, my camel route like this...

from(quartz://schedulerJob?trigger.repeatInterval=6trigger.repeatCount=+SimpleTrigger.REPEAT_INDEFINITELY).to(some
bean method ).end()

This is wht my camel route using quartz scheduler


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716261.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

Hi to all .

  I am using Camel and Quartz to schedule a job and in Quartz also i
used SimpleTrigger. But the problem here is the trigger fires while we start
the server itself, we don't want like that. It should fire on configured
time only not at initial time.
How to configure it. And the following is my configuration..

from(quartz://SchedulerJob?trigger.repeatInterval=+repeatInterval+trigger.repeatCount=+SimpleTrigger.REPEAT_INDEFINITELY)

Thanks and Regards

-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716240.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Magnus Palmér]

Unless you are on a very old version the simple trigger will not fire when
starting the route (the fireNow property)
However if your repeat interval is small it might look like that.

What I normally use is the option of delaying the start of the Quartz
scheduler itself.

Look for Starting the Quartz scheduler
http://camel.apache.org/quartz.html


2012/7/19 Sudhakar.kaithepalli sudhakar.kaithepa...@gmail.com

 Hi to all .

   I am using Camel and Quartz to schedule a job and in Quartz also
 i
 used SimpleTrigger. But the problem here is the trigger fires while we
 start
 the server itself, we don't want like that. It should fire on configured
 time only not at initial time.
 How to configure it. And the following is my configuration..


 from(quartz://SchedulerJob?trigger.repeatInterval=+repeatInterval+trigger.repeatCount=+SimpleTrigger.REPEAT_INDEFINITELY)

 Thanks and Regards

 -
 Sudhakar Kaithepalli
 --
 View this message in context:
 http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716240.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

Hi...

   How to get file size, which is there in ftp server using camel Exchange?


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716063.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Pontus Ullgren]

Hello,

The file size is available in the message headers (CamelFileLength).
See http://camel.apache.org/file2.html

// Pontus

On Mon, Jul 16, 2012 at 8:25 AM, Sudhakar.kaithepalli
sudhakar.kaithepa...@gmail.com wrote:
 Hi...

How to get file size, which is there in ftp server using camel Exchange?


 -
 Sudhakar Kaithepalli
 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716063.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

Hi Good Morning...

 Thanks for ur response Pontus...
But i don't want to interact with Active-MQ in between camel route and FTP
server. And on more thing How can i get no. of files in FTP server through
camel route? plz tell me its very urgent to me..

ThanksRegards..
Sudhakar Kaithepalli



-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716030.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Pontus Ullgren]

Hi,

For the frequency I belive you can use the Throttler pattern.
http://camel.apache.org/throttler.html

For volume you can write a RoutePolicy to suspend/resume the routes
when certain condtitions met.
See http://camel.apache.org/routepolicy.html and
http://camel.apache.org/route-throttling-example.html

I guess you could also write your own processor that simply checks if
the condition in met and then blocks for a period of time.

// Pontus


On Fri, Jul 13, 2012 at 10:13 AM, Sudhakar.kaithepalli
sudhakar.kaithepa...@gmail.com wrote:
 Hi,

 In my project, i used camel and  quartz for scheduling. For time base its
 working fine.But for frequency and volume based scheduling i don't have any
 idea.Please Help me regarding camel route creation for either for frequency
 based or for volume based. Here frequency means no. of files and volume
 means file size...

 Thanks
 Sudhakar K

 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

Hi Pontus ...

  ThankQ for ur reply Pontus ..


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5715999.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Sudhakar.kaithepalli]

HI.

   Actually my requirement is i've  a sheduler table in DB.in that
end-user store frequency as 10 files, every time we need to check with FTP
during camel route if  FTP contain =10 files then only we can start actual
task..
This is my requirement..

Thanks and Regards.
Sudhakar Kaithepalli


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716001.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel+quartz schedulers

[Pontus Ullgren]

Ok then I misunderstood your question.

In your case a PollingConsumerPollStrategy [1] might be more suitable.
But I guess it could also be achieved by using a route policy that
starts the FTP route once the correct number of files are present.

[1] http://camel.apache.org/polling-consumer.html

// Pontus


On Fri, Jul 13, 2012 at 1:54 PM, Sudhakar.kaithepalli
sudhakar.kaithepa...@gmail.com wrote:
 HI.

Actually my requirement is i've  a sheduler table in DB.in that
 end-user store frequency as 10 files, every time we need to check with FTP
 during camel route if  FTP contain =10 files then only we can start actual
 task..
 This is my requirement..

 Thanks and Regards.
 Sudhakar Kaithepalli


 -
 Sudhakar Kaithepalli
 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716001.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz and support for quartz 2.x

[Claus Ibsen]

Maybe in Camel 2.11 we can upgrade to quartz 2.x.

Then if people use Spring and Quartz together, they may have to use Spring 3.1.

Any thoughts?


On Thu, May 24, 2012 at 5:32 AM, Claus Ibsen claus.ib...@gmail.com wrote:
 On Wed, May 23, 2012 at 11:48 PM, Romain Manni-Bucau
 rmannibu...@gmail.com wrote:
 Hi,

 normally spring 3.1 supports quartz 2


 Yeah but Spring 3.0 does not. And Camel have to support Spring 3.0 onwards.


 - Romain


 2012/5/23 Christian Müller christian.muel...@gmail.com

 Nestor, please have a look at
 https://issues.apache.org/jira/browse/CAMEL-4075
 As long as Spring doesn't support Quartz 2.x, we also want to stick with
 Quartz 1.x.

 Best,
 Christian

 On Sun, May 20, 2012 at 9:00 PM, Nestor Urquiza nestor.urqu...@gmail.com
 wrote:

  Yes they are incompatible as there are several changes in 2.x. In this
 case
  what is failing is CrontTrigger is now an interface rather than a class.
 
  I will need to interact with quartz 1.x API to provide information about
  tasks, jobs and triggers.
 
  --
  View this message in context:
 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
  Sent from the Camel - Users mailing list archive at Nabble.com.
 




 --
 Claus Ibsen
 -
 CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
 FuseSource
 Email: cib...@fusesource.com
 Web: http://fusesource.com
 Twitter: davsclaus, fusenews
 Blog: http://davsclaus.blogspot.com/
 Author of Camel in Action: http://www.manning.com/ibsen/



-- 
Claus Ibsen
-
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: camel-quartz and support for quartz 2.x

[Christian Müller]

+1 for waiting until Spring 3.1 is the default version (2.11. or 3.0.) and
it supports Quartz 2.x

Best,
Christian

Sent from a mobile device
Am 24.05.2012 08:25 schrieb Claus Ibsen claus.ib...@gmail.com:

 Maybe in Camel 2.11 we can upgrade to quartz 2.x.

 Then if people use Spring and Quartz together, they may have to use Spring
 3.1.

 Any thoughts?


 On Thu, May 24, 2012 at 5:32 AM, Claus Ibsen claus.ib...@gmail.com
 wrote:
  On Wed, May 23, 2012 at 11:48 PM, Romain Manni-Bucau
  rmannibu...@gmail.com wrote:
  Hi,
 
  normally spring 3.1 supports quartz 2
 
 
  Yeah but Spring 3.0 does not. And Camel have to support Spring 3.0
 onwards.
 
 
  - Romain
 
 
  2012/5/23 Christian Müller christian.muel...@gmail.com
 
  Nestor, please have a look at
  https://issues.apache.org/jira/browse/CAMEL-4075
  As long as Spring doesn't support Quartz 2.x, we also want to stick
 with
  Quartz 1.x.
 
  Best,
  Christian
 
  On Sun, May 20, 2012 at 9:00 PM, Nestor Urquiza 
 nestor.urqu...@gmail.com
  wrote:
 
   Yes they are incompatible as there are several changes in 2.x. In
 this
  case
   what is failing is CrontTrigger is now an interface rather than a
 class.
  
   I will need to interact with quartz 1.x API to provide information
 about
   tasks, jobs and triggers.
  
   --
   View this message in context:
  
 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
   Sent from the Camel - Users mailing list archive at Nabble.com.
  
 
 
 
 
  --
  Claus Ibsen
  -
  CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
  FuseSource
  Email: cib...@fusesource.com
  Web: http://fusesource.com
  Twitter: davsclaus, fusenews
  Blog: http://davsclaus.blogspot.com/
  Author of Camel in Action: http://www.manning.com/ibsen/



 --
 Claus Ibsen
 -
 CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
 FuseSource
 Email: cib...@fusesource.com
 Web: http://fusesource.com
 Twitter: davsclaus, fusenews
 Blog: http://davsclaus.blogspot.com/
 Author of Camel in Action: http://www.manning.com/ibsen/

Re: camel-quartz and support for quartz 2.x

[Nestor Urquiza]

+1 for also adding more fields to the quartz component so persisted quartz
jobs are not rescheduled.

BTW I cannot speak for all components but so far what I have tested has been
under Spring 3.1.0-RELEASE and camel-2.9-2. Everything looks fine so far.

I hope quartz will support iCalendar, please vote if you are interested
(read http://forums.terracotta.org/forums/posts/list/0/6293.page#35127) but
in the meanwhile being able to support quartz2.x will at least allow to use
http://code.google.com/p/jwatch/ as I said.

Great 

--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5713518.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz and support for quartz 2.x

[Christian Müller]

Nestor, please have a look at
https://issues.apache.org/jira/browse/CAMEL-4075
As long as Spring doesn't support Quartz 2.x, we also want to stick with
Quartz 1.x.

Best,
Christian

On Sun, May 20, 2012 at 9:00 PM, Nestor Urquiza nestor.urqu...@gmail.comwrote:

 Yes they are incompatible as there are several changes in 2.x. In this case
 what is failing is CrontTrigger is now an interface rather than a class.

 I will need to interact with quartz 1.x API to provide information about
 tasks, jobs and triggers.

 --
 View this message in context:
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
 Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz and support for quartz 2.x

[Romain Manni-Bucau]

Hi,

normally spring 3.1 supports quartz 2

- Romain


2012/5/23 Christian Müller christian.muel...@gmail.com

 Nestor, please have a look at
 https://issues.apache.org/jira/browse/CAMEL-4075
 As long as Spring doesn't support Quartz 2.x, we also want to stick with
 Quartz 1.x.

 Best,
 Christian

 On Sun, May 20, 2012 at 9:00 PM, Nestor Urquiza nestor.urqu...@gmail.com
 wrote:

  Yes they are incompatible as there are several changes in 2.x. In this
 case
  what is failing is CrontTrigger is now an interface rather than a class.
 
  I will need to interact with quartz 1.x API to provide information about
  tasks, jobs and triggers.
 
  --
  View this message in context:
 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
  Sent from the Camel - Users mailing list archive at Nabble.com.
 

Re: camel-quartz and support for quartz 2.x

[Nestor Urquiza]

I ended up using quartz 1 but not from Camel anyway as posted here
http://camel.465427.n5.nabble.com/Configure-Camel-to-consume-externally-configured-quartz-jobs-td5712732.html

I use persistence and the quartz api to schedule jobs that call Camel routes
but I opted not to use the camel-quartz component. I will start using it if
it supports my use case which it does not at the moment.

Thank you guys for coming back with your feedback,

-Nestor

--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5713445.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-quartz and support for quartz 2.x

[Claus Ibsen]

On Wed, May 23, 2012 at 11:48 PM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
 Hi,

 normally spring 3.1 supports quartz 2


Yeah but Spring 3.0 does not. And Camel have to support Spring 3.0 onwards.


 - Romain


 2012/5/23 Christian Müller christian.muel...@gmail.com

 Nestor, please have a look at
 https://issues.apache.org/jira/browse/CAMEL-4075
 As long as Spring doesn't support Quartz 2.x, we also want to stick with
 Quartz 1.x.

 Best,
 Christian

 On Sun, May 20, 2012 at 9:00 PM, Nestor Urquiza nestor.urqu...@gmail.com
 wrote:

  Yes they are incompatible as there are several changes in 2.x. In this
 case
  what is failing is CrontTrigger is now an interface rather than a class.
 
  I will need to interact with quartz 1.x API to provide information about
  tasks, jobs and triggers.
 
  --
  View this message in context:
 
 http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
  Sent from the Camel - Users mailing list archive at Nabble.com.
 




-- 
Claus Ibsen
-
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: camel-quartz and support for quartz 2.x

[Nestor Urquiza]

Yes they are incompatible as there are several changes in 2.x. In this case
what is failing is CrontTrigger is now an interface rather than a class.

I will need to interact with quartz 1.x API to provide information about
tasks, jobs and triggers.

--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-and-support-for-quartz-2-x-tp5712613p5712679.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz consumer doesn't allow underscores?

[jsnyder]

Thank you very much Claus.

--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Quartz-consumer-doesn-t-allow-underscores-tp5063734p5072569.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel Quartz consumer doesn't allow underscores?

[Claus Ibsen]

Hi

I looked into this and noticed a bug
https://issues.apache.org/jira/browse/CAMEL-4769

The reason is we use URI#getHost() on the input uri, and using
underscores in a host name is not a valid host name, and the JDK
returns null.


On Sat, Dec 10, 2011 at 7:37 AM, jsnyder torrentar...@yahoo.com wrote:
 Given the consumer pattern:
 quartz://groupName/timerName/job.name=jobNamecron=30+15+22+*+*+?

 I would expect the a timer part of the group groupName, with the name of
 timerName, and a job name of jobName to go off every day at 22:15:30.
 Typically speaking, it does.

 When setting up a route definition, if the quartz consumer's group name
 contains an underscore, I receive the following error:

 Error building routes.  Error is:
 org.apache.camel.FailedToCreateRouteException: Failed to create route
 my.route.id: Route[[From[quartz://group_name/myTimer/?job.n... because of
 Failed to resolve endpoint:
 quartz://group_name/myTimer/?cron=0+15+18+*+*+%3Fjob.name=job_name due to:
 Trigger name cannot be null or empty.

 When I do not use an underscores, I do not receive an error, and everything
 works as expected.  I have searched through numerous articles, but have yet
 to find anything related.

 Is this a known issue?  Defect?  Or expected?

 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Camel-Quartz-consumer-doesn-t-allow-underscores-tp5063734p5063734.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: Camel-Quartz Configuration

[Ioannis Canellos]

Why would you make your life difficult and write a pojo to get files via
ftp?

I would suggest that you use a camel-ftp consumer and specigy the poll delay
to be one minute:

 route
 from 
uri=ftp://scott@localhost/public/reports?password=tigeramp;binary=trueamp;consumer.delay=6/
 to uri=the endpoint of your choice/

/route

I wouldn't use camel-quartz for that, since ftp provides a polling consumer.

A use case for camel-quartz is that if you want to retrieve data via a
producer (e.g. hit via http a url and process the results every minute).
If you still want to do it with camel-quartz here is an example:

 route
 from uri=quartz://timerName?trigger.repeatInterval=6/
 to uri=the endpoint of your choice/

/route


route
from uri=quartz://myTimerName?trigger.repeatInterval=6/
!-- The rest of the route --
/route

But I wouldn't recommend that.

I would also suggest that you take a look at the full source examples of
camel in action, which can be found here:
http://code.google.com/p/camelinaction/source/browse/trunk/?r=310
Chapter 2: Contains FTP examples.

-- 
*Ioannis Canellos*
*
FuseSource http://fusesource.com

**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer  PMC
Apache ServiceMix http://servicemix.apache.org/  Committer
Apache Gora http://incubator.apache.org/gora/ Committer
*

Re: camel-quartz 2.6.0 and multiple bundles

[Claus Ibsen]

Hi

Yeah we should have fixed/improved that in Camel 2.7 onwards. If you
check the release notes there is some tidbits about this
http://camel.apache.org/camel-270-release.html

On Thu, Jul 7, 2011 at 3:36 PM, tnk jus...@gmail.com wrote:
 Hi,

  I have two bundles (in servicemix) using camel quartz.
 The first one has route trigerred by quartz
 from(quartz://MyTimer...).to(uri).
 And the second bundle has route, which uses
 org.apache.camel.routepolicy.quartz.CronScheduledRoutePolicy with
 routeStartTime and routeStop time.

 I noticed, that sometimes route in a second bundle is not stopped/started at
 defined times, no quartz events are fired. And it happens when first bundle
 is uninstalled.

 In logs I see, that after the first bundle was uninstalled, camel quartz
 component stopped:

 2011-07-07 14:33:05,266 | INFO  | Timer-2          | QuartzComponent
 | component.quartz.QuartzComponent | 221 - camel-quartz - 2.6.0.fuse-00-00 |
 There are no more
  jobs registered, so shutting down Quartz scheduler: DefaultQuartzScheduler
 2011-07-07 14:33:05,268 | INFO  | Timer-2          | QuartzScheduler
 | org.quartz.core.QuartzScheduler  | 179 -
 org.apache.servicemix.bundles.quartz - 1.8.3.2 | Sc
 heduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.

 Am I missing something, or it is not possible to use quartz schedullers in
 multiple bundles?


 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/camel-quartz-2-6-0-and-multiple-bundles-tp4561075p4561075.html
 Sent from the Camel - Users mailing list archive at Nabble.com.




-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Re: camel-quartz and unique timername

[Claus Ibsen]

On Fri, Oct 15, 2010 at 3:28 PM, Bengt Rodehav be...@rodehav.com wrote:
 I'm using camel-quartz (Camel 2.4) and have some problems with the timer
 name (part of the URI).

 It seems that if I have two different routes (using camel-quartz) with the
 same timername, only one of the quartz endpoints will be activated, e g:

 from(quartz://mytimername?cron=0+*+*+*+*+?+*).to(endpoint1)

 from(quartz://mytimername?cron=30+*+*+*+*+?+*).to(endpoint2)


 If I make sure that the timernames are unique, both quartz endpoints will
 work. Thus I conclude that the timername must be unique (maybe this is a
 quartz thing and not a camel-quartz thing).

 However, I get no indication that something is wrong since the camel route
 is started and looks fine although the quartz endpoint will never trigger.
 This is not a good situation. In my case I use this for monitoring purposes.
 I thought that the monitoring worked fine but it was actually never
 triggered at all.

 I'm not sure if this due to camel-quartz or quartz itself. However, if it is
 possible for camel-quartz to determine that the endpoint was created OK (not
 OK if duplicate timer names), then this should case the camel context to
 fail.

 I run this in an OSGi environment (Karaf 1.6.0). Thus routes like the above
 can be created independent of each other which makes it hard to guarantee
 that the timername is unique.


Create a ticket about this, then we can validate in camel that the
timer name is unique.


 /Bengt




-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Re: camel-quartz and unique timername

[Bengt Rodehav]

JIRA created: https://issues.apache.org/activemq/browse/CAMEL-3239

https://issues.apache.org/activemq/browse/CAMEL-3239/Bengt

2010/10/15 Claus Ibsen claus.ib...@gmail.com

 On Fri, Oct 15, 2010 at 3:28 PM, Bengt Rodehav be...@rodehav.com wrote:
  I'm using camel-quartz (Camel 2.4) and have some problems with the timer
  name (part of the URI).
 
  It seems that if I have two different routes (using camel-quartz) with
 the
  same timername, only one of the quartz endpoints will be activated, e g:
 
  from(quartz://mytimername?cron=0+*+*+*+*+?+*).to(endpoint1)
 
  from(quartz://mytimername?cron=30+*+*+*+*+?+*).to(endpoint2)
 
 
  If I make sure that the timernames are unique, both quartz endpoints will
  work. Thus I conclude that the timername must be unique (maybe this is a
  quartz thing and not a camel-quartz thing).
 
  However, I get no indication that something is wrong since the camel
 route
  is started and looks fine although the quartz endpoint will never
 trigger.
  This is not a good situation. In my case I use this for monitoring
 purposes.
  I thought that the monitoring worked fine but it was actually never
  triggered at all.
 
  I'm not sure if this due to camel-quartz or quartz itself. However, if it
 is
  possible for camel-quartz to determine that the endpoint was created OK
 (not
  OK if duplicate timer names), then this should case the camel context to
  fail.
 
  I run this in an OSGi environment (Karaf 1.6.0). Thus routes like the
 above
  can be created independent of each other which makes it hard to guarantee
  that the timername is unique.
 

 Create a ticket about this, then we can validate in camel that the
 timer name is unique.


  /Bengt
 



 --
 Claus Ibsen
 Apache Camel Committer

 Author of Camel in Action: http://www.manning.com/ibsen/
 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/
 Twitter: http://twitter.com/davsclaus

Re: camel quartz

[Claus Ibsen]

On Fri, Jan 8, 2010 at 10:37 AM, marcin80 mtros...@gmail.com wrote:

 Hi

 I would like to know how to create quartz jobs dynamically? My case is
 following:
 I have a message consumer witch consume messages from queue and each message
 should be proces at specific time defined in message property. So I would
 like use somethig like this:

 route
  from uri=activemq:queue:test/
  !-- here I would like to create quartz jobs for each message triggering
 message processing in specific time but I don't know how to do it (maybe it
 is impossible?)--

 /route

 Can I do it?


How long time in the future should those tasks be executed? It will
assume its better to keep the messages in the JMS Broker until the
time is due before they are visible for the consumers. JMS have such a
feature. Cant remember exact details about it.

Anyway you can use regular Quartz to schedule tasks. So just route to
a bean or Processor and do the code in Java to schedule it with
Quartz.
To continue routing the message from that task you can use
ProducerTemplate to send it back to Camel.

We do however have a ticket about being able to send a message to
camel-quartz endpoint and have it schedule the tasks for the future
and which destination to send to
https://issues.apache.org/activemq/browse/CAMEL-1185

Use the JIRA voting system to let us know which tickets is important
for the community.

And as always we love contributions so if anyone is up for it then try
make that feature and submit patches to back to Apache.


 Cheers,
 Marcin
 --
 View this message in context: 
 http://old.nabble.com/camel-quartz-tp27073449p27073449.html
 Sent from the Camel - Users mailing list archive at Nabble.com.





-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Re: camel quartz

[marcin80]

Hi Claus, 

Thank you  for your response.

Time interval will be changeable for each task but range is 1 day - 1 week. 

Cheers,
Marcin
-- 
View this message in context: 
http://old.nabble.com/camel-quartz-tp27073449p27075754.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel quartz

[Claus Ibsen]

On Fri, Jan 8, 2010 at 2:14 PM, marcin80 mtros...@gmail.com wrote:

 Hi Claus,

 Thank you  for your response.

 Time interval will be changeable for each task but range is 1 day - 1 week.


Ah okay then I assume you can use some sort of persistent quartz to
store the trigger time and the message content.
Then you need a database to store that. But then quartz should be able
to schedule and trigger those jobs accordingly.

I was just looking if you would keep that info in memory only and thus
suffer from lost messages in case of crash etc.
So keeping the messages on the JMS Broker would then be a better choice.

But the persistent of quartz will do as well.


 Cheers,
 Marcin
 --
 View this message in context: 
 http://old.nabble.com/camel-quartz-tp27073449p27075754.html
 Sent from the Camel - Users mailing list archive at Nabble.com.





-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Re: Camel Quartz

[Willem Jiang]

Hi Charles,

I don't think the route rule will work for you.
Please remember if your rule has the
camel:to ref=queueReportingEndpoint /
will send the message body to your report queue, not receive the message 
for the report queue.


Maybe you need find other way to trigge the jms consumer.

Willem

Charles Moulliard wrote:

Hi,

I have configured my route to use quartz as a job scheduler to read the
content of my queue every 5 minutes but unfortunately, the body type send to
marshal endpoint is of type JobDetail and not List as expected.

09:30:02,545 | INFO  | heduler_Worker-1 | x3s  |
rg.apache.camel.processor.Logger   88 | Exchange[
, BodyType:org.quartz.JobDetail
, Body:JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false
, CaughtExceptionType:java.lang.ClassCastException,
CaughtExceptionMessage:org.quartz.JobDetail,
StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
at
org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)
at
org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:52)

Is my configuration wrong ?

camel:route errorHandlerRef=txErrorHandler
camel:from
uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
camel:to ref=queueReportingEndpoint /
camel:transacted ref=PROPAGATION_REQUIRED /
camel:doTry
camel:filter
camel:simplebody is java.util.List/camel:simple
/camel:filter
camel:marshal ref=csvAuditBindyDataFormat /
camel:to ref=fileReportingEndpoint /
camel:doCatch
camel:exceptionjava.lang.Exception/camel:exception
camel:to
uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
/
camel:rollback /
/camel:doCatch
/camel:doTry
/camel:route

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*
blog : http://cmoulliard.blogspot.com

Re: Camel Quartz

[Claus Ibsen]

On Fri, Aug 21, 2009 at 10:50 AM, Willem Jiangwillem.ji...@gmail.com wrote:
 Hi Charles,

 I don't think the route rule will work for you.
 Please remember if your rule has the
 camel:to ref=queueReportingEndpoint /
 will send the message body to your report queue, not receive the message for
 the report queue.

 Maybe you need find other way to trigge the jms consumer.


.pollEnrich can consume for a endpoint.


 Willem

 Charles Moulliard wrote:

 Hi,

 I have configured my route to use quartz as a job scheduler to read the
 content of my queue every 5 minutes but unfortunately, the body type send
 to
 marshal endpoint is of type JobDetail and not List as expected.

 09:30:02,545 | INFO  | heduler_Worker-1 | x3s
  |
 rg.apache.camel.processor.Logger   88 | Exchange[
 , BodyType:org.quartz.JobDetail
 , Body:JobDetail

 'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
 jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
 isVolatile: false isDurable: false requestsRecovers: false
 , CaughtExceptionType:java.lang.ClassCastException,
 CaughtExceptionMessage:org.quartz.JobDetail,
 StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
    at

 org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)
    at

 org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:52)

 Is my configuration wrong ?

        camel:route errorHandlerRef=txErrorHandler
            camel:from
 uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
            camel:to ref=queueReportingEndpoint /
            camel:transacted ref=PROPAGATION_REQUIRED /
            camel:doTry
                camel:filter
                    camel:simplebody is java.util.List/camel:simple
                /camel:filter
                camel:marshal ref=csvAuditBindyDataFormat /
                camel:to ref=fileReportingEndpoint /
                camel:doCatch
                    camel:exceptionjava.lang.Exception/camel:exception
                    camel:to

 uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
 /
                    camel:rollback /
                /camel:doCatch
            /camel:doTry
        /camel:route

 Regards,

 Charles Moulliard
 Senior Enterprise Architect
 Apache Camel Committer

 *
 blog : http://cmoulliard.blogspot.com






-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Re: Camel Quartz

[Charles Moulliard]

So I will try to use a delayer between the queue and the reporting service :

   camel:from ref=queueReportingEndpoint /
   camel:transacted ref=PROPAGATION_REQUIRED /
   camel:delayconstant360/constant/camel:delay -- to
delay 1H

BTW : It should be interesting to link (like in a job) the starting/stopping
of a Camel route to a scheduler and to offer the possibity to link routes
together depending if the job succeed (= route) or fail. With such feature,
we can use also Camel as Spring Barch to handle jobs 

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*
blog : http://cmoulliard.blogspot.com


On Fri, Aug 21, 2009 at 10:50 AM, Willem Jiang willem.ji...@gmail.comwrote:

 Hi Charles,

 I don't think the route rule will work for you.
 Please remember if your rule has the
 camel:to ref=queueReportingEndpoint /
 will send the message body to your report queue, not receive the message
 for the report queue.

 Maybe you need find other way to trigge the jms consumer.

 Willem


 Charles Moulliard wrote:

 Hi,

 I have configured my route to use quartz as a job scheduler to read the
 content of my queue every 5 minutes but unfortunately, the body type send
 to
 marshal endpoint is of type JobDetail and not List as expected.

 09:30:02,545 | INFO  | heduler_Worker-1 | x3s
  |
 rg.apache.camel.processor.Logger   88 | Exchange[
 , BodyType:org.quartz.JobDetail
 , Body:JobDetail

 'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
 jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
 isVolatile: false isDurable: false requestsRecovers: false
 , CaughtExceptionType:java.lang.ClassCastException,
 CaughtExceptionMessage:org.quartz.JobDetail,
 StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
at

 org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)
at

 org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:52)

 Is my configuration wrong ?

camel:route errorHandlerRef=txErrorHandler
camel:from
 uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
camel:to ref=queueReportingEndpoint /
camel:transacted ref=PROPAGATION_REQUIRED /
camel:doTry
camel:filter
camel:simplebody is java.util.List/camel:simple
/camel:filter
camel:marshal ref=csvAuditBindyDataFormat /
camel:to ref=fileReportingEndpoint /
camel:doCatch
camel:exceptionjava.lang.Exception/camel:exception
camel:to

 uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
 /
camel:rollback /
/camel:doCatch
/camel:doTry
/camel:route

 Regards,

 Charles Moulliard
 Senior Enterprise Architect
 Apache Camel Committer

 *
 blog : http://cmoulliard.blogspot.com

Re: Camel Quartz

[Charles Moulliard]

Claus,

You mean to create a route like this :

A) Option 1

   camel:from
uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
  camel:to ref=queueReportingEndpoint /
  camel:pollEnrich uri=/
  camel:marshal ref=csvAuditBindyDataFormat /
  camel:to ref=fileReportingEndpoint /

Question :
- In my case, no enrichement is planned so which information must be put to
replace 
- How can we define the delay in spring DSL ?

OR

B) Option 2

from ref=queueReportingEndpoint /
  camel:pollEnrich uri=/

Remark : In spring DSL, pollEnrich only accepts an uri but not a ref !!

Is this approach better than using delayer EIP ?


Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*
blog : http://cmoulliard.blogspot.com


On Fri, Aug 21, 2009 at 10:57 AM, Claus Ibsen claus.ib...@gmail.com wrote:

 On Fri, Aug 21, 2009 at 10:50 AM, Willem Jiangwillem.ji...@gmail.com
 wrote:
  Hi Charles,
 
  I don't think the route rule will work for you.
  Please remember if your rule has the
  camel:to ref=queueReportingEndpoint /
  will send the message body to your report queue, not receive the message
 for
  the report queue.
 
  Maybe you need find other way to trigge the jms consumer.
 

 .pollEnrich can consume for a endpoint.


  Willem
 
  Charles Moulliard wrote:
 
  Hi,
 
  I have configured my route to use quartz as a job scheduler to read the
  content of my queue every 5 minutes but unfortunately, the body type
 send
  to
  marshal endpoint is of type JobDetail and not List as expected.
 
  09:30:02,545 | INFO  | heduler_Worker-1 | x3s
   |
  rg.apache.camel.processor.Logger   88 | Exchange[
  , BodyType:org.quartz.JobDetail
  , Body:JobDetail
 
 
 'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
  jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
  isVolatile: false isDurable: false requestsRecovers: false
  , CaughtExceptionType:java.lang.ClassCastException,
  CaughtExceptionMessage:org.quartz.JobDetail,
  StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
 at
 
 
 org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)
 at
 
 
 org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:52)
 
  Is my configuration wrong ?
 
 camel:route errorHandlerRef=txErrorHandler
 camel:from
  uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
 camel:to ref=queueReportingEndpoint /
 camel:transacted ref=PROPAGATION_REQUIRED /
 camel:doTry
 camel:filter
 camel:simplebody is java.util.List/camel:simple
 /camel:filter
 camel:marshal ref=csvAuditBindyDataFormat /
 camel:to ref=fileReportingEndpoint /
 camel:doCatch
 
  camel:exceptionjava.lang.Exception/camel:exception
 camel:to
 
 
 uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
  /
 camel:rollback /
 /camel:doCatch
 /camel:doTry
 /camel:route
 
  Regards,
 
  Charles Moulliard
  Senior Enterprise Architect
  Apache Camel Committer
 
  *
  blog : http://cmoulliard.blogspot.com
 
 
 



 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/
 Twitter: http://twitter.com/davsclaus

Re: Camel Quartz

[Charles Moulliard]

I have tried this :

camel:route errorHandlerRef=txErrorHandler
camel:from
uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
camel:pollEnrich uri=queuingservice:x3s:reporting/
camel:transacted ref=PROPAGATION_REQUIRED /
camel:marshal ref=csvAuditBindyDataFormat /
camel:to ref=fileReportingEndpoint /

but the error is still there :

12:35:02,451 | INFO  | heduler_Worker-1 | x3s  |
rg.apache.camel.processor.Logger   88 | Exchange[
, BodyType:org.quartz.JobDetail
, Body:JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false
, CaughtExceptionType:java.lang.ClassCastException,
CaughtExceptionMessage:org.quartz.JobDetail,
StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
at
org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*
blog : http://cmoulliard.blogspot.com


On Fri, Aug 21, 2009 at 12:25 PM, Charles Moulliard cmoulli...@gmail.comwrote:

 Claus,

 You mean to create a route like this :

 A) Option 1

camel:from
 uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
   camel:to ref=queueReportingEndpoint /
   camel:pollEnrich uri=/
   camel:marshal ref=csvAuditBindyDataFormat /
   camel:to ref=fileReportingEndpoint /

 Question :
 - In my case, no enrichement is planned so which information must be put to
 replace 
 - How can we define the delay in spring DSL ?

 OR

 B) Option 2

 from ref=queueReportingEndpoint /
   camel:pollEnrich uri=/

 Remark : In spring DSL, pollEnrich only accepts an uri but not a ref !!

 Is this approach better than using delayer EIP ?


 Charles Moulliard
 Senior Enterprise Architect
 Apache Camel Committer

 *
 blog : http://cmoulliard.blogspot.com


 On Fri, Aug 21, 2009 at 10:57 AM, Claus Ibsen claus.ib...@gmail.comwrote:

 On Fri, Aug 21, 2009 at 10:50 AM, Willem Jiangwillem.ji...@gmail.com
 wrote:
  Hi Charles,
 
  I don't think the route rule will work for you.
  Please remember if your rule has the
  camel:to ref=queueReportingEndpoint /
  will send the message body to your report queue, not receive the message
 for
  the report queue.
 
  Maybe you need find other way to trigge the jms consumer.
 

 .pollEnrich can consume for a endpoint.


  Willem
 
  Charles Moulliard wrote:
 
  Hi,
 
  I have configured my route to use quartz as a job scheduler to read the
  content of my queue every 5 minutes but unfortunately, the body type
 send
  to
  marshal endpoint is of type JobDetail and not List as expected.
 
  09:30:02,545 | INFO  | heduler_Worker-1 | x3s
   |
  rg.apache.camel.processor.Logger   88 | Exchange[
  , BodyType:org.quartz.JobDetail
  , Body:JobDetail
 
 
 'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
  jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
  isVolatile: false isDurable: false requestsRecovers: false
  , CaughtExceptionType:java.lang.ClassCastException,
  CaughtExceptionMessage:org.quartz.JobDetail,
  StackTrace:java.lang.ClassCastException: org.quartz.JobDetail
 at
 
 
 org.apache.camel.dataformat.bindy.csv.BindyCsvDataFormat.marshal(BindyCsvDataFormat.java:60)
 at
 
 
 org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:52)
 
  Is my configuration wrong ?
 
 camel:route errorHandlerRef=txErrorHandler
 camel:from
  uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
 camel:to ref=queueReportingEndpoint /
 camel:transacted ref=PROPAGATION_REQUIRED /
 camel:doTry
 camel:filter
 camel:simplebody is java.util.List/camel:simple
 /camel:filter
 camel:marshal ref=csvAuditBindyDataFormat /
 camel:to ref=fileReportingEndpoint /
 camel:doCatch
 
  camel:exceptionjava.lang.Exception/camel:exception
 camel:to
 
 
 uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
  /
 camel:rollback /
 /camel:doCatch
 /camel:doTry
 /camel:route
 
  Regards,
 
  Charles Moulliard
  Senior Enterprise Architect
  Apache Camel Committer
 
  *
  blog : http://cmoulliard.blogspot.com
 
 
 



 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/
 Twitter: http://twitter.com/davsclaus

Re: Camel Quartz

[Charles Moulliard]

I have also created the following route + aggregator

camel:route errorHandlerRef=txErrorHandler
camel:from
uri=quartz://x3sReporting/clientError?cron=0+0/5+9-18+?+*+MON-FRI/
camel:pollEnrich uri=queuingservice:x3s:reporting
strategyRef=queueAggregator/
camel:transacted ref=PROPAGATION_REQUIRED /
camel:doTry
camel:marshal ref=csvAuditBindyDataFormat /
camel:to ref=fileReportingEndpoint /
camel:doCatch
camel:exceptionjava.lang.Exception/camel:exception
camel:to
uri=log:com.xpectis.x3s?level=INFOamp;multiline=trueamp;showException=trueamp;showCaughtException=trueamp;showStackTrace=true
/
camel:rollback /
/camel:doCatch
/camel:doTry
/camel:route

bean id=queueAggregator
class=com.xpectis.x3s.core.util.QueueAggregator/

but error :

13:10:02,013 | INFO  | heduler_Worker-1 | TraceInterceptor |
rg.apache.camel.processor.Logger   88 |
ID-dell-charles-1326-1250837959638-0-92 
from(quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI) --
ref:PROPAGATION_REQUIRED, Pattern:InOnly, Headers:{previousFireTime=null,
nextFireTime=Fri Aug 21 13:15:00 CEST 2009,
scheduler=org.quartz.impl.stdschedu...@785ad7, triggerGroup=x3sReporting,
trigger=Trigger 'x3sReporting.clientError':  triggerClass:
'org.quartz.CronTrigger isVolatile: false calendar: 'null'
misfireInstruction: 0 nextFireTime: Fri Aug 21 13:15:00 CEST 2009,
mergedjobdatamap=org.quartz.jobdata...@ccc462dc, scheduledFireTime=Fri Aug
21 13:10:00 CEST 2009, fireTime=Fri Aug 21 13:10:00 CEST 2009,
jobDetail=JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false, calendar=null,
jobinstance=org.apache.camel.component.quartz.camel...@1940ed6, result=null,
jobRunTime=-1, triggerName=clientError, refireCount=0},
BodyType:org.quartz.JobDetail, Body:JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false
13:10:02,013 | INFO  | heduler_Worker-1 | TraceInterceptor |
rg.apache.camel.processor.Logger   88 |
ID-dell-charles-1326-1250837959638-0-92  ref:PROPAGATION_REQUIRED --
Try, Pattern:InOnly, Headers:{previousFireTime=null, nextFireTime=Fri Aug 21
13:15:00 CEST 2009, scheduler=org.quartz.impl.stdschedu...@785ad7,
triggerGroup=x3sReporting, trigger=Trigger 'x3sReporting.clientError':
triggerClass: 'org.quartz.CronTrigger isVolatile: false calendar: 'null'
misfireInstruction: 0 nextFireTime: Fri Aug 21 13:15:00 CEST 2009,
mergedjobdatamap=org.quartz.jobdata...@ccc462dc, scheduledFireTime=Fri Aug
21 13:10:00 CEST 2009, fireTime=Fri Aug 21 13:10:00 CEST 2009,
jobDetail=JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false, calendar=null,
jobinstance=org.apache.camel.component.quartz.camel...@1940ed6, result=null,
jobRunTime=-1, triggerName=clientError, refireCount=0},
BodyType:org.quartz.JobDetail, Body:JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false
13:10:02,029 | INFO  | heduler_Worker-1 | TraceInterceptor |
rg.apache.camel.processor.Logger   88 |
ID-dell-charles-1326-1250837959638-0-92  Try --, Pattern:InOnly,
Headers:{previousFireTime=null, nextFireTime=Fri Aug 21 13:15:00 CEST 2009,
scheduler=org.quartz.impl.stdschedu...@785ad7, triggerGroup=x3sReporting,
trigger=Trigger 'x3sReporting.clientError':  triggerClass:
'org.quartz.CronTrigger isVolatile: false calendar: 'null'
misfireInstruction: 0 nextFireTime: Fri Aug 21 13:15:00 CEST 2009,
mergedjobdatamap=org.quartz.jobdata...@ccc462dc, scheduledFireTime=Fri Aug
21 13:10:00 CEST 2009, fireTime=Fri Aug 21 13:10:00 CEST 2009,
jobDetail=JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false, calendar=null,
jobinstance=org.apache.camel.component.quartz.camel...@1940ed6, result=null,
jobRunTime=-1, triggerName=clientError, refireCount=0},
BodyType:org.quartz.JobDetail, Body:JobDetail
'DEFAULT.quartz://x3sReporting/clientError?cron=0+0%2F5+9-18+%3F+*+MON-FRI':
jobClass: 'org.apache.camel.component.quartz.CamelJob isStateful: false
isVolatile: false isDurable: false requestsRecovers: false
13:10:02,435 | INFO  | heduler_Worker-1 | TraceInterceptor |

Re: Camel-quartz

[Claus Ibsen]

Hi

I have created the ticket and is currently improving the quartz component.
Yeah its a real bummer with the / as cron separators. I have improved
it to be a URI parameter instead, only requiring to use _ as space.

eg:
quartz://myGroup/myTimerName?cron=0_0/5_12-18_?_*_MON-FRI
quartz://myGroup/myTimerName?cron=0_0_*_*_*_?

And we can use ? instead of having to use $. So its only _ as spaces.



On Fri, Feb 27, 2009 at 3:58 PM, Claus Ibsen claus.ib...@gmail.com wrote:
 On Fri, Feb 27, 2009 at 2:48 PM, gmagniez gabriel.magn...@steria.com wrote:

 Hi,
 The camel-quartz component replace the character / by  , but how can i
 use the / in the cron expression like from trigering something every five
 minutes: 0/5?
 I've found another thread about that problem but it was not resolved.
 http://www.nabble.com/camel-quartz-cron-trigger-endpoint-uri-syntax-td13923344.html#a13923344
 Hi

 Yeah I can not see the reason for this replacement unless to divide
 into sub paths, for each individual cron element.

 Do you mind creating a ticket, then we can fix it so you can use / in
 the URI. The only one that is reasonable to replace is the ? with $
 otherwise, even thought it may still be valid URI using it.
 http://camel.apache.org/support.html


 Best regards
 --
 View this message in context: 
 http://www.nabble.com/Camel-quartz-tp22246214p22246214.html
 Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.





 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/




-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/

Re: Camel-quartz

[Hadrian Zbarcea]

I think using '+' for a space is a common convention and better than a  
'_'.

$0.02
Hadrian

On Feb 28, 2009, at 10:29 AM, Claus Ibsen wrote:


Hi

The ticket:
https://issues.apache.org/activemq/browse/CAMEL-1407

Implemented in Camel 2.0

On Sat, Feb 28, 2009 at 4:06 PM, Claus Ibsen claus.ib...@gmail.com  
wrote:

Hi

I have created the ticket and is currently improving the quartz  
component.

Yeah its a real bummer with the / as cron separators. I have improved
it to be a URI parameter instead, only requiring to use _ as space.

eg:
quartz://myGroup/myTimerName?cron=0_0/5_12-18_?_*_MON-FRI
quartz://myGroup/myTimerName?cron=0_0_*_*_*_?

And we can use ? instead of having to use $. So its only _ as spaces.



On Fri, Feb 27, 2009 at 3:58 PM, Claus Ibsen  
claus.ib...@gmail.com wrote:
On Fri, Feb 27, 2009 at 2:48 PM, gmagniez gabriel.magn...@steria.com 
 wrote:


Hi,
The camel-quartz component replace the character / by  , but  
how can i
use the / in the cron expression like from trigering something  
every five

minutes: 0/5?
I've found another thread about that problem but it was not  
resolved.

http://www.nabble.com/camel-quartz-cron-trigger-endpoint-uri-syntax-td13923344.html#a13923344

Hi

Yeah I can not see the reason for this replacement unless to divide
into sub paths, for each individual cron element.

Do you mind creating a ticket, then we can fix it so you can use /  
in

the URI. The only one that is reasonable to replace is the ? with $
otherwise, even thought it may still be valid URI using it.
http://camel.apache.org/support.html



Best regards
--
View this message in context: 
http://www.nabble.com/Camel-quartz-tp22246214p22246214.html
Sent from the Camel - Users (activemq) mailing list archive at  
Nabble.com.







--
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/





--
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/





--
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/

Re: Camel-quartz

[Claus Ibsen]

On Sat, Feb 28, 2009 at 5:06 PM, Hadrian Zbarcea hzbar...@gmail.com wrote:
 I think using '+' for a space is a common convention and better than a '_'.
Okay lets support them both, using _ is much easier to read instead of +.
Try a complex cron with - and using + as separators is not easy to read.

 $0.02
 Hadrian

 On Feb 28, 2009, at 10:29 AM, Claus Ibsen wrote:

 Hi

 The ticket:
 https://issues.apache.org/activemq/browse/CAMEL-1407

 Implemented in Camel 2.0

 On Sat, Feb 28, 2009 at 4:06 PM, Claus Ibsen claus.ib...@gmail.com
 wrote:

 Hi

 I have created the ticket and is currently improving the quartz
 component.
 Yeah its a real bummer with the / as cron separators. I have improved
 it to be a URI parameter instead, only requiring to use _ as space.

 eg:
 quartz://myGroup/myTimerName?cron=0_0/5_12-18_?_*_MON-FRI
 quartz://myGroup/myTimerName?cron=0_0_*_*_*_?

 And we can use ? instead of having to use $. So its only _ as spaces.



 On Fri, Feb 27, 2009 at 3:58 PM, Claus Ibsen claus.ib...@gmail.com
 wrote:

 On Fri, Feb 27, 2009 at 2:48 PM, gmagniez gabriel.magn...@steria.com
 wrote:

 Hi,
 The camel-quartz component replace the character / by  , but how
 can i
 use the / in the cron expression like from trigering something every
 five
 minutes: 0/5?
 I've found another thread about that problem but it was not resolved.

 http://www.nabble.com/camel-quartz-cron-trigger-endpoint-uri-syntax-td13923344.html#a13923344

 Hi

 Yeah I can not see the reason for this replacement unless to divide
 into sub paths, for each individual cron element.

 Do you mind creating a ticket, then we can fix it so you can use / in
 the URI. The only one that is reasonable to replace is the ? with $
 otherwise, even thought it may still be valid URI using it.
 http://camel.apache.org/support.html


 Best regards
 --
 View this message in context:
 http://www.nabble.com/Camel-quartz-tp22246214p22246214.html
 Sent from the Camel - Users (activemq) mailing list archive at
 Nabble.com.





 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/




 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/




 --
 Claus Ibsen
 Apache Camel Committer

 Open Source Integration: http://fusesource.com
 Blog: http://davsclaus.blogspot.com/





-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/

Re: Camel-quartz

[Claus Ibsen]

On Fri, Feb 27, 2009 at 2:48 PM, gmagniez gabriel.magn...@steria.com wrote:

 Hi,
 The camel-quartz component replace the character / by  , but how can i
 use the / in the cron expression like from trigering something every five
 minutes: 0/5?
 I've found another thread about that problem but it was not resolved.
 http://www.nabble.com/camel-quartz-cron-trigger-endpoint-uri-syntax-td13923344.html#a13923344
Hi

Yeah I can not see the reason for this replacement unless to divide
into sub paths, for each individual cron element.

Do you mind creating a ticket, then we can fix it so you can use / in
the URI. The only one that is reasonable to replace is the ? with $
otherwise, even thought it may still be valid URI using it.
http://camel.apache.org/support.html


 Best regards
 --
 View this message in context: 
 http://www.nabble.com/Camel-quartz-tp22246214p22246214.html
 Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.





-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/