[
https://issues.apache.org/jira/browse/CAMEL-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677037#comment-17677037
]
Simon Rasmussen commented on CAMEL-16956:
-----------------------------------------
Another solution which only uses a single route:
{code:java}
from(aws2Sqs("input.fifo")).threads(1,5,200).to("slow");
{code}
This achieves same as above workaround. This can be used together with
extendMessageVisibility and maxMessagesPerPoll to increase throughput.
The consumer will immediately forward the message(s) to the threads EIP and
begin the next poll.
> Camel AWS SQS: Really supports concurrent consumers
> ---------------------------------------------------
>
> Key: CAMEL-16956
> URL: https://issues.apache.org/jira/browse/CAMEL-16956
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 3.x
>
>
> At the moment the concurrent consumers value is set on the consumer
> scheduler. We need to do something like we are doing in camel-nats, where we
> define a poolSize for the executor Services and spin up concurrent consumers
> based on this value and an executor service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
