Hi, I've got one more question about the reading of the documentation: Aggregator (http://camel.apache.org/aggregator.html) has a attribute "batchTimeout":
batchTimeout: Timeout in millis. How long should the aggregator wait before its completed and sends whatever it has currently aggregated. 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). When there is a lot of variance of the arrival time of messages, than (b) gives me a lot more latency than it would be necessary. What is the intended behavior? Kind regards, Frank -- View this message in context: http://www.nabble.com/Aggregator-batchTimeout-tp23127654p23127654.html Sent from the Camel - Users mailing list archive at Nabble.com.
