You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ben Maes (Jira)" <ji...@apache.org> on 2021/09/14 12:38:00 UTC

[jira] [Commented] (CAMEL-16956) Camel AWS SQS: Really supports concurrent consumers

    [ https://issues.apache.org/jira/browse/CAMEL-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414914#comment-17414914 ] 

Ben Maes commented on CAMEL-16956:
----------------------------------

Current workaround I used to fix this:
{code:java}
from(aws2Sqs("input.fifo"))
.to(seda("test").blockWhenFull(true));

from(seda("test").size(1).concurrentConsumers(5))
to("slow");
{code}

> 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-sqs
>            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.3.4#803005)