camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Okhotnikov <>
Subject Re: File component blocked by existing files
Date Mon, 12 Oct 2009 08:15:23 GMT

Yes, I known about the readLockTimeout option. The problem with this option
is that by a) default it waits forever and b) while it waits for one file it
does not process others. That's what made me spend 2 days wondering about
the behavior described in the thread almost without clues, and it will made

As is pretty well explained in the "Release It" book, infinite waits are
bad. Infinite waits by default are very bad, especially in integration
software - it virtually guarantees that at least one will slip into your
live system, then it's just a matter of time until it blocks critical
function or critical amount of resources - and you're waken in the middle of
the night to deal with it.

What do you think?

Claus Ibsen-2 wrote:
> You can already do this by the readLockTimeout option. See more details
> here:
> For example you can set it to 10000 as 10 seconds and if Camel cannot
> acquire the lock within that period it will skip this file and try the
> next one.
> -- 
> Claus Ibsen
> Apache Camel Committer
> Open Source Integration:
> Blog:
> Twitter:

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

View raw message