[
https://issues.apache.org/jira/browse/CAMEL-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-15244.
--------------------------------------
Resolution: Fixed
> AggregationStrategy - default timeout method should be empty
> ------------------------------------------------------------
>
> Key: CAMEL-15244
> URL: https://issues.apache.org/jira/browse/CAMEL-15244
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 3.4.0
> Reporter: Claus Ibsen
> Assignee: Andrea Cosentino
> Priority: Major
> Labels: help-wanted
> Fix For: 3.5.0, 3.4.3
>
>
> As reported on gitter
> Hi, I've noticed we get the following warning when using
> groupedBodyAggregationStrategy with sjms-batch.
> 2020-06-25 22:49:19.522 WARN ||| 21068 --- [msBatchConsumer]
> o.a.c.p.a.GroupedBodyAggregationStrategy : Parallel processing timed out
> after 500 millis for number 18. This task will be cancelled and will not be
> aggregated.
> I think it comes from this default interface implementation on
> AggregationStrategy.
> default void timeout(Exchange exchange, int index, int total, long
> timeout) {
> // log a WARN we timed out since it will not be aggregated and the
> Exchange will be lost
> LoggerFactory.getLogger(getClass()).warn("Parallel processing timed
> out after {} millis for number {}. This task will be cancelled and will not
> be aggregated.", timeout, index);
> }
> I think the warning is wrong as the aggregated messages do seem to come
> through. It is just annoying in the logs. I can change log level for this
> category to error but I'm concerned there may be genuine info that will be
> hidden. Any thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
