Torsten, thank you for confirming my findings. So, essentially the aggregator waits the specified batchTimeout milliseconds, aggregates whatever it finds on the queue and then waits for the next round.
This is not quite what I was expecting - or to put it differently: Is there a way to aggregate messages that vary considerable in their arriving times? Kind regards Frank tmi wrote: > > It is rather option b). The aggregator will take all aggregated messages > after the specified timeout and send it in one message (exchange). > -- View this message in context: http://www.nabble.com/Aggregator-batchTimeout-tp23127654p23137098.html Sent from the Camel - Users mailing list archive at Nabble.com.
