Hi Kalyan, this issue is known. See https://issues.apache.org/jira/browse/CAMEL-8419 . CAMEL-8419 contains even a patch. But this patch is more a workaround, therefore this patch was never merged.
Best Regards Franz On Wed, Dec 16, 2015 at 12:35 PM, calyan.bandi <calyan.ba...@gmail.com> wrote: > Hi, > > I found the anwer to the problem in apache cxf forums. > > http://cxf.547215.n5.nabble.com/How-to-increase-the-max-size-of-a-REST-response-td563077.html > > This is more of a issue in the CXF component than camel. But still for > referene, i am sharing this information. > > At the server side, we saw the below response headers for each of the > requests. > > ID: 2 > Response-Code: 200 > Content-Type: application/json > Headers: {Content-Type=[application/json], Date=[Wed, 16 Dec 2015 11:21:34 > GMT]} > Messages: Outbound Message (saved to tmp file): > Filename: C:\Users\Temp\cxf-tmp-309797\cos8635606649006238176tmp > (message truncated to 65536 bytes) > > And from the client logs, whatever the payload that is received from the > server, we are seeing only the first chunk in the logs (calculated the > response payload size from 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: > http://camel.465427.n5.nabble.com/Camel-Stream-caching-unable-to-capture-the-entire-stream-tp5775055p5775145.html > Sent from the Camel - Users mailing list archive at Nabble.com.
