Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.219.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1358341213355-5725641.post@n5.nabble.com>
References: <1358268602079-5725581.post@n5.nabble.com>
	<CAGB5yN=BgTtNqk9d2VHg-Tg8y2Lq2FLHVckbNMsPogOiswHwhg@mail.gmail.com>
	<1358341213355-5725641.post@n5.nabble.com>
Date: Thu, 17 Jan 2013 00:47:14 +0100
Message-ID: 
 <CALvzYd-XEqvYX9dfBZiK=AVO-acF51-ZvMic9n2tJraxxOLxUg@mail.gmail.com>
Subject: Re: Concat routes
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=e89a8f839dfb75d49804d3707f01

--e89a8f839dfb75d49804d3707f01
Content-Type: text/plain; charset=ISO-8859-1

I guess the behavior is different because the quartz component use the
inOnly MEP and the servlet component use the inOut  MEP. I cannot check
this at present...

Best,
Christian

Sent from a mobile device
Am 16.01.2013 14:00 schrieb "klauss42" <klaus.schroeder@ethalon.de>:

> Hi Claus
>
> > What do you mean by parallel?
>
> The 3 routes (vm:invoiceMapping, vm:invoiceControl + vm:invoiceAccounting)
> get started in parallel when the cron starts the vm:invoiceProcessing
> route.
> Here is some log output of a test that hopefully explains the behavior:
>
> Routes "called" sequentially when launched via servlet:
> 2013-01-16 13:50:29,701 [INFO ][invoiceMapping] - Job 'invoiceMapping'
> started
> 2013-01-16 13:50:29,769 [INFO ][invoiceMapping] - Executing step:
> [invoiceMappingStep]
> 2013-01-16 13:50:29,781 [INFO ][invoiceMapping] - invoiceMapping started
> 2013-01-16 13:50:30,781 [INFO ][invoiceMapping] - working 0 sec
> 2013-01-16 13:50:31,781 [INFO ][invoiceMapping] - working 1 sec
> ..
> 2013-01-16 13:50:34,781 [INFO ][invoiceMapping] - invoiceMapping ended
> 2013-01-16 13:50:34,809 [INFO ][invoiceMapping] - Job 'invoiceMapping'
> completed
> 2013-01-16 13:50:34,851 [INFO ][invoiceControl] - Job 'invoiceControl'
> started
> 2013-01-16 13:50:34,870 [INFO ][invoiceControl] - Executing step:
> [invoiceControlStep]
> 2013-01-16 13:50:34,878 [INFO ][invoiceControl] - invoiceControl started
> 2013-01-16 13:50:35,879 [INFO ][invoiceControl] - working 0 sec
> 2013-01-16 13:50:36,879 [INFO ][invoiceControl] - working 1 sec
> ...
> 2013-01-16 13:50:44,881 [INFO ][invoiceControl] - invoiceControl ended
> 2013-01-16 13:50:44,919 [INFO ][invoiceControl] - Job 'invoiceControl'
> completed
> 2013-01-16 13:50:44,958 [INFO ][invoiceAccounting] - Job
> 'invoiceAccounting'
> started
> 2013-01-16 13:50:44,979 [INFO ][invoiceAccounting] - Executing step:
> [invoiceAccountingStep]
> 2013-01-16 13:50:44,994 [INFO ][invoiceAccounting] - invoiceAccounting
> started
> 2013-01-16 13:50:45,995 [INFO ][invoiceAccounting] - working 0 sec
> 2013-01-16 13:50:46,995 [INFO ][invoiceAccounting] - working 1 sec
> ...
> 2013-01-16 13:50:54,997 [INFO ][invoiceAccounting] - invoiceAccounting
> ended
> 2013-01-16 13:50:55,032 [INFO ][invoiceAccounting] - Job
> 'invoiceAccounting'
> completed
>
>
> Routes "called" in parallel execution when launched via quartz:
> 2013-01-16 11:57:33,132 [INFO ][invoiceControl] - Job 'invoiceControl'
> started
> 2013-01-16 11:57:33,132 [INFO ][invoiceAccounting] - Job
> 'invoiceAccounting'
> started
> 2013-01-16 11:57:33,132 [INFO ][invoiceMapping] - Job 'invoiceMapping'
> started
> 2013-01-16 11:57:33,185 [INFO ][invoiceAccounting] - Executing step:
> [invoiceAccountingStep]
> 2013-01-16 11:57:33,221 [INFO ][invoiceAccounting] - invoiceAccounting
> started
> 2013-01-16 11:57:33,221 [INFO ][invoiceControl] - invoiceControl started
> 2013-01-16 11:57:33,221 [INFO ][invoiceMapping] - invoiceMapping started
> 2013-01-16 11:57:34,222 [INFO ][invoiceAccounting] - working 0 sec
> 2013-01-16 11:57:34,223 [INFO ][invoiceControl] - working 0 sec
> 2013-01-16 11:57:34,226 [INFO ][invoiceMapping] - working 0 sec
> 2013-01-16 11:57:35,222 [INFO ][invoiceAccounting] - working 1 sec
> 2013-01-16 11:57:35,224 [INFO ][invoiceControl] - working 1 sec
> 2013-01-16 11:57:35,227 [INFO ][invoiceMapping] - working 1 sec
> 2013-01-16 11:57:36,222 [INFO ][invoiceAccounting] - working 2 sec
> 2013-01-16 11:57:36,224 [INFO ][invoiceControl] - working 2 sec
> 2013-01-16 11:57:36,228 [INFO ][invoiceMapping] - working 2 sec
> 2013-01-16 11:57:37,222 [INFO ][invoiceAccounting] - working 3 sec
> 2013-01-16 11:57:37,224 [INFO ][invoiceControl] - working 3 sec
> ...
>
> In this log output you can see that all 3 routes get fired at the same time
> instead of being executed one after the other. I do not understand why
> Camel
> behaves different if triggered by Quartz. The intended behavior is the
> sequential execution of the routes.
>
>
> >  How frequent have you set the cron job to trigger?
>
> The cron is set to run once per night only.
>
> >
> > I think you can set quartz stateful=true, so it wont trigger new jobs
> > while previous jobs are still active.
>
> No, I am already using stateful=true and that only prevents multiple
> parallel executions of the same scheduled route.
>
> > Maybe that is what you mean by parallel?
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Concat-routes-tp5725581p5725641.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--e89a8f839dfb75d49804d3707f01--