camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Does Camel respect another context's readLock?
Date Fri, 05 Nov 2010 09:10:19 GMT
There is a rollback in the DSL you can use (albeit its based on
exception as well)

On Fri, Nov 5, 2010 at 9:57 AM, Andreas A. <> wrote:
> Hi
> Yeah I agree, I use include/exclude in other areas but here I cannot since I
> don't have any control over the naming of the remote files. I have to look
> at their payload to determine it. Also sometimes files are not even "for me"
> so I have to roll those back too. I've been thinking about looking into
> org.apache.camel.component.file.GenericFileProcessStrategy to see if I can
> use for a cleaner way to roll back a file, instead of abusing exceptions for
> this behaviour.
> I discovered the real problem though, which was a matter of me sending a
> reference of the file to a seda route, then the original route ended and
> tried to rename the file to the .camel directory. Sometimes this would cause
> a race condition because an aggregator in the seda-route was using the file
> reference also.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Twitter: davsclaus
Author of Camel in Action:

View raw message