That's the beauty of the stream resequencer, it allows the messages to go one by one as they get ordered and the difference in speed is very little for the overall process. The batch aggregator waits for all the exchanges to completed and then it send them to the aggregator, which will bring additional delays. Another way would be to know how many messages arrived in the bean and keep the last one away just before being aggregated until all the rest are aggregated, but you might end up with pretty complex routes.
-- View this message in context: http://camel.465427.n5.nabble.com/count-of-processed-messages-when-using-aggregation-tp5742649p5743212.html Sent from the Camel - Users mailing list archive at Nabble.com.
