Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.18.3
-
None
-
Unknown
Description
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:
{{ // check for timed out aggregated messages once every second timeoutMap = new AggregationTimeoutMap(getTimeoutCheckerExecutorService(), 1000L);}}
because it's hardcoded to 1s.
A new option like timeoutCheckerExecutorInterval with default value of 1000ms will solve the problem.