[
https://issues.apache.org/jira/browse/CAMEL-16791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474677#comment-17474677
]
Karen Lease commented on CAMEL-16791:
-------------------------------------
[~jeremyross] I guess that could cause such behavior. Then what I'd expect is
if the inbound is running in a single thread, that thread would also be used to
execute the outbound API call so it would basically slow down the processing to
match what the remote can handle. So for example, you might see one aggregate
being completed by the Aggregator thread but following ones being completed by
the thread sending events to the aggregator (pool-3-thread3 in the test case
log below.)
{code:java}
[Camel (camel-1) thread #1 - Aggregator] TRACE AggregateProcessor -
Aggregated exchange onComplete: Exchange[DEB82B7F5DE944A-00000000000000D7]
[pool-3-thread-3 ] TRACE AggregateProcessor -
Aggregated exchange onComplete: Exchange[DEB82B7F5DE944A-00000000000000D9]{code}
Unless your inbound side is already multi-threaded, maybe it would be
interesting to use an aggregator thread pool with more threads.
> camel-core - Aggregate EIP defaults to a worker queue size of 1000
> ------------------------------------------------------------------
>
> Key: CAMEL-16791
> URL: https://issues.apache.org/jira/browse/CAMEL-16791
> Project: Camel
> Issue Type: Improvement
> Components: came-core
> Affects Versions: 3.11.0
> Reporter: Jeremy Ross
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.15.0
>
>
> Perhaps should default to 1, or make it easily globally configured.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
