Return-Path: 
 <users-return-46628-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 E4F5910B9D
	for <apmail-camel-users-archive@www.apache.org>;
 Mon,  3 Feb 2014 14:52:42 +0000 (UTC)
Received: (qmail 7032 invoked by uid 500); 3 Feb 2014 14:52:41 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 6987 invoked by uid 500); 3 Feb 2014 14:52:40 -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 6979 invoked by uid 99); 3 Feb 2014 14:52:39 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Feb 2014 14:52:39 +0000
X-ASF-Spam-Status: No, hits=2.8 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Received: from [209.85.214.43] (HELO mail-bk0-f43.google.com) (209.85.214.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Feb 2014 14:52:33 +0000
Received: by mail-bk0-f43.google.com with SMTP id mx11so2893863bkb.2
        for <users@camel.apache.org>; Mon, 03 Feb 2014 06:52:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-type;
        bh=zJS5ylbExO4hyILDkSeCmTwrFgbnOw03UAH7zrNAOVI=;
        b=XxF/RIuaq31iFa2X4Eo4UNoriENcBMY7Y70oizgMSYv6oHB25Q0z73Di9Qw57oOI8O
         /akT4NU8QX4GLSwQPU+3pCSonYbIU9OpRamajZWYCc2A5joN04AYBTynp/QwHf3Bh0Uw
         RSa6pN0oxQlaW+Q+nzSUeluYbYQB0CJY5kScg7gunN6MSaziJ5yu8krK7u9KpoSyfm73
         uf5N4aWM+5gLDvIFhRV/1iPjiC+51qIJgKoPemuCKPLBx8oLIhuY7JY65IynRMJhCsiC
         oVBxsqvnUpldk3eajAH4QW4pG+P67sH2n0Ym+4FwtzvAdJOndnSDoToGlCbYMoioEoci
         vjSA==
X-Gm-Message-State: 
 ALoCoQlHFwCDMMNd9ohyST2jJIybmLK7X96Y3ynK56AmPD2vIDXHl6/xuQJ48dMSGpiFEqpDB2GW
MIME-Version: 1.0
X-Received: by 10.205.25.6 with SMTP id rg6mr10030963bkb.10.1391439132831;
 Mon, 03 Feb 2014 06:52:12 -0800 (PST)
Received: by 10.204.224.76 with HTTP; Mon, 3 Feb 2014 06:52:12 -0800 (PST)
In-Reply-To: 
 <cbb4b75d4b6746cd89664de677efd9e8@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
References: 
 <CAHLNkZud7HuuGpo2i7L5CCg6ao1Nm-Z+iawUiW7nx_hsCkgtYA@mail.gmail.com>
	<CAGB5yNnenut485uORNfQiZLxajeB_eR9vkdM41hucSJLyg7V+g@mail.gmail.com>
	<CAHLNkZs-DpCqmGVCPhkK-iFNP9WNEkk9C+641tMYLoH6euobrw@mail.gmail.com>
	<cbb4b75d4b6746cd89664de677efd9e8@DB3PR01MB300.eurprd01.prod.exchangelabs.com>
Date: Mon, 3 Feb 2014 15:52:12 +0100
Message-ID: 
 <CAHLNkZvVxQ-E65tX=Sd=Bh1Y4itjy_f0mzRws34oCbjHtHmkKw@mail.gmail.com>
Subject: Re: Quartz in cluster
From: Tom Fornoville <tom.fornoville@roots.be>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=20cf301e2e153d9e3804f181ab22
X-Virus-Checked: Checked by ClamAV on apache.org

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

Thanks Claus & Ronny!

Since we're using JBoss Fuse 6.0 we cannot use camel 2.12 features yet
(waiting on the 6.1 release).

If I understand correctly once we upgrade we can specify  our route like
this (provided that the quartz scheduler was configured to use a
jbdc-jobstore):
  <from uri"sftp://{{user}}@{{server}}?password={{password}}&amp;scheduler=quartz2&scheduler.cron=..."
/>

The <pollEnrich> seems to be a solution also but since we're expecting Fuse
6. any day now I'd like to give that a try first.
I'll let you know how it goes.

Kind regards,
Tom

Tom Fornoville
Senior Developer
m: +32 478 65 86 51
www.roots.be


On Mon, Feb 3, 2014 at 3:31 PM, Ronny Aerts <ronny.aerts@intris.be> wrote:

> Hello Tom,
>
> Could the pollEnrich help you?
>
> <from uri="quartz:..." />
> <pollEnrich uri="sftp://{{user}}@{{server}}?password={{password}}"/>
>
> --
> Kind regards,
> Ronny Aerts - Intris nv - Wapenstilstandlaan 47, 2600 Berchem, Belgium
> R&D Integration Architect
> Prince II certified
> Tel: +32-3-326.50.75
> -----Original Message-----
> From: Tom Fornoville [mailto:tom.fornoville@roots.be]
> Sent: maandag 3 februari 2014 15:07
> To: users@camel.apache.org
> Subject: Re: Quartz in cluster
>
> Hi Claus,
>
> Thanks for your answer.
> I read that topic earlier but it's not the configuration of Quartz I'm
> having problems with.
>
> What I would like to know is how I can use a quartz endpoint to trigger
> file pickup.
>
> Right now we have something like:
>   <route>
>       <from uri="sftp://{{user}}@
> {{server}}?password={{password}}&amp;delay={{delay}}"/>
>       ...
>   </route>
>
> And we want to replace the delay with a Quartz scheduler so it should be
> something like:
>   <route>
>       <from uri="quartz:..." />
>       <from uri="sftp://{{user}}@{{server}}?password={{password}}"/>
>       ...
>   </route>
>
> The second <from> doesn't make sense but I don't know how to describe what
> I want this route to do.
>
> Tom Fornoville
> Senior Developer
> m: +32 478 65 86 51
> www.roots.be
>
>
> On Mon, Feb 3, 2014 at 2:52 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>
> > Hi
> >
> > A similar topic was recently debated
> >
> > http://camel.465427.n5.nabble.com/Master-Slave-failover-using-database
> > -lock-tp5746646.html
> >
> > On Mon, Feb 3, 2014 at 2:46 PM, Tom Fornoville
> > <tom.fornoville@roots.be>
> > wrote:
> > > Hello Camel users,
> > >
> > > In our project we have several routes that start from a file (local
> > > filesystem or FTP) and when we're clustering this via Fuse Fabric we
> > > want to ensure that only one instance of the route picks up files.
> > >
> > > Our first thought was to use the Quartz scheduler with a
> > > JDBC-JobStore as described here:
> > >
> > http://quartz-scheduler.org/documentation/quartz-2.x/configuration/Con
> > figJDBCJobStoreClustering
> > >
> > > Is there an example of a working JDBC-JobStore from within Camel?
> > >
> > > Are there other (simpler) solutions to make sure that multiple
> > > routes
> > don't
> > > interfere?
> > >
> > > Best regards,
> > > Tom
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email: cibsen@redhat.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen Make your
> > Camel applications look hawt, try: http://hawt.io
> >
> Intris nv
> Wapenstilstandlaan 47
> B-2600 Berchem
>         Tel.  +32 3 326 50 75
> Fax  +32 3 326 42 23
> www.intris.be<http://www.intris.be/>
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this
> communication is intended solely for use by the individual or entity to
> whom it is addressed.
> Use of this communication by others is prohibited. If the e-mail message
> was sent to you by mistake, please notify support@intris.be<mailto:
> support@intris.be>, destroy it without reading, using, copying or
> disclosing its contents to any other person.
> We accept no liability for damage related to data and/or documents which
> are communicated by electronic mail.
>

--20cf301e2e153d9e3804f181ab22--