Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.216.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=p1HXTEXwXop3a0XJh2WKf61LQe9hXlEVyneE/fda/06bRJGh2sWzLSxQQAGBL87W39
         By20MEygop31/u4IrCeXRFvOlF89ODfbH+/z6PXl0PrYUD79Tue2EVfI+2oT1VNuDOGN
         YGDL862IhZC/0Ub/0D/1Tslg0kqNt+M9Pj1ik=
MIME-Version: 1.0
In-Reply-To: <2E5E061E-86D3-4CE0-AF59-B94F7CA95AE1@tataryn.net>
References: <2E5E061E-86D3-4CE0-AF59-B94F7CA95AE1@tataryn.net>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 7 Oct 2010 17:33:41 +0200
Message-ID: <AANLkTinN6s_-aL_-Vn1d4iokNw06HqcvzxYbHJEysfRT@mail.gmail.com>
Subject: Re: File Component readLock strategy
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

Its actually a bit tricky to detect if a file is locked by another
process or not.
Although we have the java.nio API it seems to not work consistent
across OS's. And I actually think its stated in the docs somewhere,
that this can be the case.

Also note that NIO locks is JVM wide, which means from an unit test
you cannot lock a file by one thread, and from the same JVM see the
file lock.
And if you forget to unlock the NIO lock, that file is locked until
you restart the JVM. Can be a caveat for big app servers, if you have
a rouge app holding a lock.

Then you can try to obtain the lock on the file by trying to rename it
before reading, if you can rename then you assume the other party is
not currently writing to it.
But I think some OS and apps may allow the OS to rename a file which
currently is being written by that app.

That leaves you with checking the file modification and timestamp and
wait until its "steady".

But NIO 2 should have a file watcher API. I assume it may be better at
providing notifications when a file has been finished writing.
So we can wait for Java 7 :)


On Thu, Oct 7, 2010 at 1:07 AM, Craig Tataryn <craiger@tataryn.net> wrote:
> Has anyone had any luck using a readLock strategy other than "changed"? =
=A0I've tried them all, and "changed" seems to be the only one that works c=
onsistently when I'm copying a large file into a directory the File Compone=
nt is monitoring.
>
> All other's allow the File Component to execute before the file is comple=
tely copied into the directory.
>
> $mvn -X --version
> Apache Maven 3.0-beta-3 (r990787; 2010-08-30 07:44:03-0500)
> Java version: 1.6.0_20
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Hom=
e
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac"
>
> Craig.
>
> --
> Craig Tataryn
> site: http://www.basementcoders.com/
> podcast: http://www.basementcoders.com/?feed=3Dpodcast
> itunes: http://itunes.apple.com/podcast/the-basement-coders
> irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin
> twitter: craiger
>
>


--=20
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus