Hi Claus, I aplogise for not understanding your comments (mutate the existing oldExchange). Please help me understand if you have sometime.
I am doing as I did because of the following ... 1. I guess that the old exchange is null only once for every aggregation block (i.e Since I have the completion size as 50000, the old exchange will be null once every 5000 data). I guess this would not be a overhead causing the outage. 2. Since there is no defauls converter to StringBuilder, I had to make the oldExchange contents as StringBuilder as it enhances the performance by a big margin. But now have come to a conclusion that Java cannot handle this big a data (50000 payload). But the concern really is that it was not able to handle 5000 payloads. Size of a payload would be equal or less than a swaps product entity. Thanks & regards, Ebe -- View this message in context: http://camel.465427.n5.nabble.com/Java-heap-space-issue-with-Aggregation-tp5670608p5676295.html Sent from the Camel - Users mailing list archive at Nabble.com.
