[
https://issues.apache.org/jira/browse/CAMEL-11515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075230#comment-16075230
]
Claus Ibsen commented on CAMEL-11515:
-------------------------------------
Its not very good to have so low timeout values when you get sub seconds.
What is your use-case
> Aggregator is not working correctly when completionTimeout < 1000ms
> -------------------------------------------------------------------
>
> Key: CAMEL-11515
> URL: https://issues.apache.org/jira/browse/CAMEL-11515
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.18.3
> Reporter: Denis Chirov
> Attachments: AggregateExpressionTimeoutTestModified.java
>
>
> The aggregated exchange doesn't become complete after a completionTimeout
> which is lower than 1000ms (e.g. 150ms)
> From source code, seems that there is no way to set a value for
> AggregationTimeoutMap from AggregateProcessor class:
> {code}
> {{ // check for timed out aggregated messages once every second
> timeoutMap = new
> AggregationTimeoutMap(getTimeoutCheckerExecutorService(), 1000L);}}
> {code}
> because it's hardcoded to 1s.
> A new option like *timeoutCheckerExecutorInterval* with default value of
> 1000ms will solve the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
