Camel Stream Caching

Hello. Some of our old projects enable stream caching on their Camel contexts, and set some options that I'm not sure about. Most of our use cases read data from files, send them to JMS queues before transforming and processing them. Setting a value for "spoolThreshold", if I'm not wrong, forces

AW: Camel Stream caching seems not to delete the temporary files

ull}") to make sure everything is cleaned up. Thanks in advance for your help. Christian -Ursprüngliche Nachricht- Von: Claus Ibsen [mailto:claus.ib...@gmail.com] Gesendet: Dienstag, 21. November 2017 13:35 An: users@camel.apache.org Betreff: Re: Camel Stream caching seems not to delete

Re: Camel Stream caching seems not to delete the temporary files

he memory leak because now the data are written twice on >> my disk: one to the temporary directory name that I had intended and one in >> the java.io.tempdir directory. The documentation on Camel Stream-caching >> states "Camel itself will handle deleting the temporary file

Re: Camel Stream caching seems not to delete the temporary files

to > from(...= > .toD("${body}") > .streamCaching() > .to("file:" + tempDirectoryName) > > This helped with the memory leak because now the data are written twice on my > disk: one to the temporary directory name that I had intended and one in the > java.io.t

AW: Camel Stream caching seems not to delete the temporary files

th the memory leak because now the data are written twice on my disk: one to the temporary directory name that I had intended and one in the java.io.tempdir directory. The documentation on Camel Stream-caching states "Camel itself will handle deleting the temporary file once the cached strea

Camel Stream caching seems not to delete the temporary files

ten twice on my disk: one to the temporary directory name that I had intended and one in the java.io.tempdir directory. The documentation on Camel Stream-caching states "Camel itself will handle deleting the temporary file once the cached stream is no longer necessary." But I can't se

Re: Camel Stream caching unable to capture the entire stream

the logs and it is 65536 bytes). This is only a > concern during logging and in my camel routes at the client side the entire > response is getting unmarshalled from JSON and things are working fine. > > Thanks, > Kalyan > > > > -- > View this message in context: > htt

Re: Camel Stream caching unable to capture the entire stream

routes at the client side the entire response is getting unmarshalled from JSON and things are working fine. Thanks, Kalyan -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Stream-caching-unable-to-capture-the-entire-stream-tp5775055p5775145.html Sent from the Camel

Camel Stream caching unable to capture the entire stream

the entire response with which i captured the full JSON response and the size of the entire string is around 71172 bytes. Any pointers around this issue, kindly suggest. Thanks, Kalyan -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Stream-caching-unable-to-capture