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 Tue, 02 Nov 2010 17:12:32 GMT

You can use a include/exclude filter to ensure they dont compete for
the same files, which is IMHO much better.
Then A takes care of A files
And B takes care of B files

On Tue, Nov 2, 2010 at 3:05 PM, Andreas A. <> wrote:
> Hi
> I'm seeing some strange behaviour that I suspect might come from the fact
> that I have two Camel-contexts in each it's own Camel Main competing over
> the same files in a directory. What will actually happen when you let two
> effectively seperate Camel applications loose at the same directory?
> I get some nullpointer-exceptions because at some "random" point Camel reads
> an empty file and tries to perform transformations on it.
> I have this setup because I consume two types of files from a remote
> directory. Then I have two contexts take care of each type of type. If one
> context picks up an unknown type I throw an exception to roll back the file
> to the remote dir. This is probably not the greatest idea either, but the
> only one I could come up with.
> --
> 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