Return-Path: 
 <users-return-35673-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 886ABE0CB
	for <apmail-camel-users-archive@www.apache.org>;
 Wed, 16 Jan 2013 11:14:00 +0000 (UTC)
Received: (qmail 34829 invoked by uid 500); 16 Jan 2013 11:14:00 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 34649 invoked by uid 500); 16 Jan 2013 11:13:56 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 34620 invoked by uid 99); 16 Jan 2013 11:13:55 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 11:13:55 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.42 as permitted sender)
Received: from [209.85.215.42] (HELO mail-la0-f42.google.com) (209.85.215.42)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2013 11:13:51 +0000
Received: by mail-la0-f42.google.com with SMTP id fe20so1249044lab.1
        for <users@camel.apache.org>; Wed, 16 Jan 2013 03:13:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:mime-version:in-reply-to:references:from:date:message-id
         :subject:to:content-type;
        bh=iwYhXqBZ7xlaodE2qLQXH3PhVln2MybC5LR46nRxyxU=;
        b=qqDgyfAQI23yMh4QoYUtkhQeLAM3AiuZptXqw7LSX8GVTOVHWWREUR1sRc2AvKIb45
         I/SuFgxYxkM5M3dRXINWNgkDhlDkF2s23DDeaNYJKuMkhqwpjDeeqb4S1c0yObhHsLso
         j+nuuFK05XB0OhDU2mhYs3MMz6XgZwSnWzPb7nkjK3mwabIgoXroKMPDxdmQfLELgkkn
         Y7Y26Cm6y5cq8yF71ABW5x7DcfphNG2Zhx0YUvopMv3vpmHDeXVwawZWs6MvFkH/EwkI
         C7yi0DlR7SdcKUAY5aBAl0XXPIsh/KiDd0Ap+s60IVoz0Vpj2L4njwFnFCAQIltqVGBB
         jbSw==
X-Received: by 10.152.113.165 with SMTP id iz5mr699190lab.50.1358334809397;
 Wed, 16 Jan 2013 03:13:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.33.83 with HTTP; Wed, 16 Jan 2013 03:13:08 -0800 (PST)
In-Reply-To: <1358268602079-5725581.post@n5.nabble.com>
References: <1358268602079-5725581.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 16 Jan 2013 12:13:08 +0100
Message-ID: 
 <CAGB5yN=BgTtNqk9d2VHg-Tg8y2Lq2FLHVckbNMsPogOiswHwhg@mail.gmail.com>
Subject: Re: Concat routes
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

On Tue, Jan 15, 2013 at 5:50 PM, klauss42 <klaus.schroeder@ethalon.de> wrote:
> Hello Camel experts
> I have multiple routes that perform some background processing, in detail
> the routes just trigger some Spring-Batch jobs. I want to be able to start
> each single route alone, therefore I am using the Servlet component to be
> able to trigger the routes by URL.
>
> Now I wanted to concatenate the routes in a new route. The routes should be
> perfromed in sequential order. I tried multicast with
> "parallelProcessing=false" and that works fine if the new route
> "invoiceProcessingRoute" gets triggerred by the Servlet component. The
> routes get started in proper sequence. Here is an excerpt of my Camel
> config:
>
>                 <route id="invoiceProcessingServlet">
>                         <from uri="servlet:///invoiceProcessing" />
>                         <to uri="vm:invoiceProcessing?timeout=0" />
>                         <transform>
>                                 <constant>Invoice Processing job finished</constant>
>                         </transform>
>                 </route>
>
>                 <route id="invoiceProcessingRoute">
>                         <from uri="vm:invoiceProcessing" />
>                         <camel:multicast parallelProcessing="false" stopOnException="false">
>                                 <to uri="vm:invoiceMapping?timeout=0" />
>                                 <to uri="vm:invoiceControl?timeout=0" />
>                                 <to uri="vm:invoiceAccounting?timeout=0" />
>                         </camel:multicast>
>                 </route>
>
> But if I use the Quartz component to trigger the above route by a cron, the
> individual routes get started in parallel, which is not the indented
> behavior. Here is the scheduled route:
>

What do you mean by parallel? How frequent have you set the cron job to trigger?

I think you can set quartz stateful=true, so it wont trigger new jobs
while previous jobs are still active.
Maybe that is what you mean by parallel?



>                 <route id="invoiceProcessingScheduled"
> autoStartup="{{il.cron.invoiceProcessing.startup}}">
>                         <from
> uri="quartz://invoiceProcessing/?stateful=true&amp;cron={{il.cron.invoiceProcessing}}"
> />
>                         <to uri="vm:invoiceProcessing" />
>                 </route>
>
> The problem is the parallel execution. Do I misunderstand something? Is it a
> bug? What is the recommended way to start routes sequentially?
>
> Remark: In these routes I do not use the content of any messages, I just use
> Camel to start my Spring-batch jobs.
>
> Thanks for any help
> Klaus
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Concat-routes-tp5725581.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: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen