The task runs once a second. http://camel.apache.org/aggregator2
So the wiki is wrong, I will fix that. If you want a timeout after 5 seconds, then just set that value to 5 sec. Then that background tasks, which runs once per sec. will detect that its overdue (> 5 sec) and trigger completion. The Camel in Action book covers the Aggregator EIP in depth in chapter 8 (10+ pages about it) On Tue, Apr 5, 2011 at 12:50 PM, Mond Raymond <mondraym...@gmail.com> wrote: > Folks > > I am confused by the documentation: > > > Time in millis that an aggregated exchange should be inactive before its > complete. Camel has a background task that runs once a minute to check for > inactive aggregated exchanges. This option can be set as either a fixed > value or using an Expression which allows you to evaluate a timeout > dynamically - will use Long as result. If both are set Camel will fallback > to use the fixed value if the Expression result was null or 0. You cannot > use this option together with completionInterval, only one of the two can be > used. > > > > It seems that the timeout will be at least a minute. My unit tests show > that to be the case. > > > Can I set a lower timeout in another way (I would prefer it to be around 30 > seconds)? > > Thanks > > > Ray > > -- > View this message in context: > http://camel.465427.n5.nabble.com/aggregator-completionTimeout-tp4283669p4283669.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
