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 christian.mueller@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1348045196351-5719581.post@n5.nabble.com>
References: <1347898685976-5719484.post@n5.nabble.com>
	<1347962024321-5719517.post@n5.nabble.com>
	<CALvzYd8WfwAd6YGkTUVUFUsZKzFedoXk2w6PUbdhryBfg6ofpw@mail.gmail.com>
	<5058DF2D.1020709@gmail.com>
	<1348045196351-5719581.post@n5.nabble.com>
Date: Wed, 19 Sep 2012 18:48:06 +0200
Message-ID: 
 <CALvzYd_2nQwKk9vfYzCqZQaLgyGUMkv9hgdRJNninhR1jJ5tiQ@mail.gmail.com>
Subject: Re: File renaming problems under Windows
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=20cf303347db62991904ca10c5d8

--20cf303347db62991904ca10c5d8
Content-Type: text/plain; charset=ISO-8859-1

May be Smooks doesn't close the stream in a propper way?

Sent from a mobile device
Am 19.09.2012 11:00 schrieb "OrackBahama" <jdorfschmid@metadok.de>:

> Thanks Mohan, I fully agree with you - besides one point:
>
> Always checking the return value of the renameTo(...) function call is of
> no
> use if you can't rely on Windows having completed, flushed and unlocked
> everything to disk before returning this value.
>
> My experience is that even if the return value is TRUE, the underlying
> Windows rename operation (or the unlocking) still is incomplete.
>
> The correct call should have an operating system dependent option such as
> "renameToEx(..., WRITE_THROUGH=TRUE)" or
> "renameToEx(...,
> TELL_WINDOWS_TO_NOT_RETURN_UNLESS_EVERYTHING_IS_FLUSHED_AND_UNLOCKED)"
>
> Unfortunately - making heavy use of frameworks (Camel ->
> org.apache.commons...FileUtils, Smooks, ..) - I have no direct influence on
> what happens with IO calls, retry counts, close operations e.g. ...)
>
> My camel route is as simple as this:
>
>     from( "file://{{w.inbox}}?"
>         + "initialDelay={{w.polling.init.msec}}"               //15000
>         + "&delay={{w.polling.msec}}"                          //25000
>         + "&preMove={{w.inbox.pre}}"
>         + "&move={{w.backup}}/${date:now:yyyy-MM-dd}/${file:onlyname}"
>         + "&moveFailed={{w.error}}/${date:now:yyyy-MM-dd}/${file:onlyname}"
>         + "&maxMessagesPerPoll={{w.inbox.maxMsgPerPoll}}"      //10
>      )
>      .log( LoggingLevel.INFO, "imp_protocol", "Importiere Daten :
> ${file:onlyname}" )
>      .convertBodyTo( StreamSource.class )
>      .to( "smooks://smooks-config.xml" )
>      ;
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/File-renaming-problems-under-Windows-tp5719484p5719581.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--20cf303347db62991904ca10c5d8--