Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1336561489350-5697076.post@n5.nabble.com>
References: <1336132433952-5685631.post@n5.nabble.com>
 <1336134321706-5685713.post@n5.nabble.com>
 <CAGB5yNmKLD_1SB+m_FhuuitA9bpDbev1A4smUh-of9ghZ4CsRQ@mail.gmail.com>
 <1336374441220-5690355.post@n5.nabble.com>
 <1336554401574-5696843.post@n5.nabble.com>
 <CAGB5yNm1u11NzTaWxFSpqGa5-kiULK-yAGjEsYK594470Yb97Q@mail.gmail.com>
 <1336561489350-5697076.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 9 May 2012 13:08:49 +0200
Message-ID: 
 <CAGB5yNkPnkPYRyq1i-E7dZFg-_zzs6aijpciqTOHbaK+eqN0Kw@mail.gmail.com>
Subject: Re: Component file: move and moveFailed
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, May 9, 2012 at 1:04 PM, Hilde <hilde.schwed@yahoo.de> wrote:
> The files being processed with camel afterwards are not moved to that
> directory programmatically but also droped in the directory manually. As a
> result there can no open file stream remain.
>

Read about the read-lock strategies you have at
http://camel.apache.org/file2

eg the idea is to avoid reading files while other parties is currently
writing them. And that depends on what file system you use etc, what
you can do.


> --
> View this message in context: http://camel.465427.n5.nabble.com/Component-file-move-and-moveFailed-tp5685631p5697076.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/