On Tue, Oct 23, 2012 at 9:48 AM, Hilde <[email protected]> wrote: > Hello folks! > > We are using an ftp-consumer route for downloading big data. For avoiding an > OutOfMemoryException we > decided to use the option /localWorkDirectory/ with the consequences to have > just a file handle as an exchange > body (payload) instead of loading the whole file. As our tests indicate the > option works fine on Linux but crashes > on Windows. On a Windows machine it comes to troubles in rename and move the > file to its final target directory. > Could any Camel developer please verify this? >
We have unit tests with that in camel-ftp. I guess you may do something with the file in custom code or something. And you forget to close a stream or something. > Thanks in advance > Hilde > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-ftp-option-localWorkDirectory-doesn-t-work-properly-on-windows-tp5721438.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
