Update: I was able to workaround this problem using ylambert's approach (thank you sir!), however it makes me a little uneasy that the problem must be dealt with in such a way. It seems to me like this is a bug in the way Camel handles transferring a local file to a remote system with SFTP/FTP(S).
I cannot envision a case when it is appropriate to try to read the entire contents of a (large) file into a byte buffer in order to stream data over the network, and I think most people would agree this is common sense. I can only conclude that this is the product of some nuance of the TypeConverter system that I do not understand, and that it is not really meant to work this way - at least not in this case. With regards to localWorkDirectory and its usefulness in the upload scenario, I can see that this might be helpful if I was trying to send data that was already memory bound and so writing out data to a local temporary file would help things stay within memory limits. However, in my scenario the file already exists on the local disk, so I don't see how writing that file out to *another* file is going to help anything. I do appreciate the quick response Claus, I'm just guessing you thought I was dealing with the download use-case instead of the upload case. Camel still rocks; I know it is hard to please everybody and there are a LOT of components to support. Hopefully this thread helps anybody else who runs into this issue. Cheers, Mike -- View this message in context: http://camel.465427.n5.nabble.com/Errors-with-SFTP-producer-and-large-files-tp4757404p4760166.html Sent from the Camel - Users mailing list archive at Nabble.com.
