I've run into the a problem that if the File Consumer tries to process a large file (excess of 200MB) I run out of Heap Space.
Is there a way to tell the file2 Endpoint to ignore files over a certain size? Does the File Endpoint serialize the data into the message or does it just provide a pointer to the file? If the latter, is there a way to programatically inspect the size of the body of the message before loading into a byte array? I have the same questions for the ftp2 endpoint. Thank you, ~Justin -- View this message in context: http://camel.465427.n5.nabble.com/File-Consumer-Max-File-Size-tp5451246p5451246.html Sent from the Camel - Users mailing list archive at Nabble.com.
