Please find my comments inline. Best, Christian
On Tue, Sep 18, 2012 at 11:53 AM, OrackBahama <jdorfsch...@metadok.de>wrote: > Hi, > meanwhile I suspect Windows (or the Java VM, not Camel) to be the culprit > for not unlocking files immediately after renaming. There's an extended > version of the Windows MoveFile-API function (MoveFileEx) that takes extra > flags to force Windows to flush copy and delete operations to disk *before* > returning from the MoveFile function. > > It might be possible that this API call is *not used* in the current Java 6 > VM implementation. > I think it's possible to reproduce the (bad) behavior even with correctly > closed InputStreams for example with Java copy and delete operations in > quick succession. > > To be more precise, the questions are: > 1.) Is there a workaround (e.g. timeout or retry parameters) for my current > runtime config ? > I don't know. You didn't shared your runtime config until now... 2.) Are all Camel components Java 7 ready ? > Starting with Camel 2.10.0, we fully support Java 7: http://camel.apache.org/camel-2100-release.html 3.) Is this bug fixed in Java 7 ? > I don't know. I think you should ask this question on an Oracle mailing list. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File-renaming-problems-under-Windows-tp5719484p5719517.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
