...
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Option | Required | Default Value | Description |
|---|
aggregationStrategy
|  | null
| A reference to an AggregationStrategy in the Camel registry (e.g. #myAggregationStrategy) | completionSize
| | 200
| The size of the batch to aggregate. Care should be taken to ensure that this is not larger than the JMS consumer's prefetch buffer, or the maximum page size for a queue on the broker; either of these could cause the consumer to hang if no timeout is used. A value of 0 or less indicates that completionTimeout only should be used. | completionTimeout
| | 500
| The maximum time to wait from the receipt of the first message before emitting the Exchange. A value of 0 or less indicates that completionSize only should be used. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured. | completionTimeout | | | Camel 2.17: The completion interval in millis, which causes batches to be completed in a scheduled fixed rate every interval. The batch may be empty if the timeout triggered and there was no messages in the batch. Notice you cannot use both completion timeout and completion interval at the same time, only one can be configured. | sendEmptyMessageWhenIdle | | false | Camel 2.17: If using completion timeout or interval, then the batch may be empty if the timeout triggered and there was no messages in the batch. If this option is true and the batch is empty then an empty message is added to the batch so an empty message is routed. | pollDuration
| | 1000
| The maximum length of a call to MessageConsumer.receive(). The time remaining before timeout takes precedence within a batch. This value is effectively the poll time between batches. | timeoutCheckerExecutorService | | | Camel 2.17: If using the completionInterval option a background thread is created to trigger the completion interval. Set this option to provide a custom thread pool to be used rather than creating a new thread for every consumer. |
|
The completionSize endpoint attribute is used in conjunction with completionTimeout, where the first condition to be met will cause the aggregated Exchange to be emitted down the route.
...
