camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen">
Subject RE: CAMEL-250: Still having probs
Date Wed, 02 Jul 2008 04:24:28 GMT
Hi Law

The file components had some improvements from 1.3 to 1.4. As you write the lock file is removed,
even if the poll failed.

In Camel 1.5 we have planned some improvements to file and ftp component.
I do think this one also applies for the
File component as well = there needs to be some sort of "progress" strategy.

When you copy the file, a strategy also common used is to copy it with a different name, and
when the copying has finished you rename the file to the correct filename. It is then important
to instruct Camel to exclude reading "in progress" files. Camel has options to set *.work
etc. as excluded pattern.

1) So you copy the file as:
2) And set Camel to exclude *.work
3) And when finished copying the file, then you rename to mybigfile.txt

Med venlig hilsen
Claus Ibsen
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576

-----Original Message-----
From: law [] 
Sent: 1. juli 2008 21:30
Subject: Re: CAMEL-250: Still having probs

Looks like the 1.4 snapshot at least doesn't die upon having problems
renaming a file. However, it will not re-process the file automagically, but
will if I just rename it.

law wrote:
> The problem I am having is that when I copy a large file into the
> directory that camel is reading from and it hasn't finished copying, camel
> attempts to copy the file into the .camel dir which fails since the
> copying of the file is locking it since it hasn't finished. I tried to use
> the noop=true but that doesn't seem to pick up new files put in the
> directory (I really don't know what's going on w/ that). However, I was
> browsing the bugs and found:
> which seems to indicate that the problem was fixed in 1.3, but I'm still
> seeing it. Does anyone have any insights of what I can do to fix either:
> a) The noop flag for files
> b) Ignore files until they are ready to be read, then fire off the
> consumer
> c) If it is going to fail, how can I make it reprocess the file. It seems
> to kill camel when this happens.
> The setup I have is using spring bean for the .to() and having spring
> start up the context.

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message