Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
References: <CABctVUi=MJi+-acNC1gyoY7jfECy_tFKKKKnYa2XWCCBXwzUNA@mail.gmail.com>
 <CAGB5yNnUjUryPw+h3jh2CY4LOopYboh0C=37iW8GzqPZZU7EqA@mail.gmail.com>
In-Reply-To: <CAGB5yNnUjUryPw+h3jh2CY4LOopYboh0C=37iW8GzqPZZU7EqA@mail.gmail.com>
From: Stephan Burkard <sburkard@gmail.com>
Date: Mon, 13 Mar 2017 16:09:16 +0000
Message-ID: <CABctVUiBN+A65LgjS7ZBXjmvLpocYVt=XQNhtDspYQVKHmhYNg@mail.gmail.com>
Subject: Re: Camel marker files ".camelLock" not deleted
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=001a1148f5c27f5ab2054a9eeff4
archived-at: Mon, 13 Mar 2017 16:09:32 -0000

--001a1148f5c27f5ab2054a9eeff4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Zoran and Claus

Thanks for the suggestions.

readLockDeleteOrphanLockFiles: I am on Camel 2.12, so this is currently no
option.
shuffle: dito

I will look up the coordinator in the Camel book. This is a good reason to
download the most current MEAP version :-)

Regards
Stephan


Claus Ibsen <claus.ibsen@gmail.com> schrieb am Mo., 13. M=C3=A4rz 2017 um
17:02 Uhr:

> Hi
>
> You can use shuffle=3Dtrue to randomize the file order to spread the
> chance of clash.
>
> But when having competing consumers on the same file share you can end
> up with clashes.
> You can use a distributed coordinator which is covered in the 2nd ed
> of the Camel book in the transactional chapter. And as well in the
> upcoming chapter on clustering.
>
>
>
> On Mon, Mar 13, 2017 at 3:47 PM, Stephan Burkard <sburkard@gmail.com>
> wrote:
> > Hi Camel riders
> >
> > I have a quite simple polling file consumer that runs fine on 2
> instances.
> >
> > from(fileEndpointUri)
> > .routeId(routeId)
> > .log("[FILEREADER " + routeId + "], file: ${in.header.CamelFileName}")
> > .setBody(method(bomProcessor, "removeBomIfPresent"))
> > .to(jmsEndpointUri);
> >
> >
> > The fileUri options are:
> > - initialDelay=3D[random-range]
> > - delay=3D[configurable]
> > - antFilterCaseSensitive=3Dfalse
> > - antInclude=3D*.xml
> > - preMove=3Dprocessing
> > - delete=3Dtrue
> > - moveFailed=3D../error
> >
> > I generate a random start delay to avoid both consumers running at the
> same
> > time. However sometimes they overlap and want to process the same file.
> >
> > In this case I see normal processing in the logfile of one instance and
> an
> > error in the log of the other instance. So it works perfectly. With one
> > small flaw: the marker files of Camel (whatever.camelLock) are not
> deleted.
> > That makes the operation guys nervous.
> >
> > Can I do something so that these marker files are deleted? Is this kind
> of
> > a misconfiguration of my file endpoint?
> >
> > Thanks a lot
> > Stephan
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

--001a1148f5c27f5ab2054a9eeff4--