I suggest to change your aggregation code to *not* create a new DefaultExchange manually.
You should ideally just mutate the oldExchange all the time. On Thu, Apr 26, 2012 at 7:12 PM, ebinsingh <ebenezer.si...@verizonwireless.com> wrote: > Hi Claus, > > I have another issue with the aggregator. > > Hi, > > I am trying the aggregation with completionSize set to 2000. > What happens is that the first output has 2000 records, but the second > output has 4000 records instead of the next 2000 records. > > Is there someting am missing in my aggregator logic ... > Appreciate your help. > > am using the same aggregation logic given in this thread. > Thanks & regards, > Ebe > > -- > View this message in context: > http://camel.465427.n5.nabble.com/File-Name-through-Aggregator-tp5665526p5668183.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
