On Mon, Apr 20, 2009 at 1:22 PM, tmi <[email protected]> wrote: > > > Frank Schwarz wrote: >> >> How do you read it? >> (a) The aggregation is aborted after the batchTimeout, leading to possibly >> fragmentary messages. The aggregation is started, when the first message >> is available. >> (b) The aggregator waits the batchTimeout timespan and then begins the >> aggregation. Only messages that are available at this time are aggregated. >> >> I understand (a) but unfortunately observe (b). >> > > It is rather option b). The aggregator will take all aggregated messages > after the specified timeout and send it in one message (exchange). > Perhaps this article helps you as well: > http://tmielke.blogspot.com/2009_01_01_archive.html Its a very good blog post on the aggreagator. I have added links to it from the Camel aggregator EIP wiki page.
> > > -- > View this message in context: > http://www.nabble.com/Aggregator-batchTimeout-tp23127654p23134835.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
