[
https://issues.apache.org/jira/browse/CAMEL-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082888#comment-17082888
]
Claus Ibsen commented on CAMEL-14888:
-------------------------------------
Can you post more details of your Camel route etc with the aws-sqs and the
controlbus you use to control it.
Also mind that the options in SB Camel 3.2.0 is
camel.component.aws2-sqs.concurrent-consumers
https://github.com/apache/camel-spring-boot/blob/camel-spring-boot-3.2.0/components-starter/camel-aws2-sqs-starter/src/main/docs/aws2-sqs-starter.adoc
> When resuming an AWS2-SQS route using controlbus, concurrent consumers seems
> not set
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-14888
> URL: https://issues.apache.org/jira/browse/CAMEL-14888
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
> Affects Versions: 3.2.0
> Reporter: Catalin Alexandru Zamfir
> Priority: Major
>
> *Update*: when putting "concurrentConsumers" as part of the "from" string,
> the issue below doesn't manifest itself It seems to only manifest when the
> concurrent-consumers Camel/Spring properly is inside tha application.yaml
> file. Bug? Feature? The way things should be? The issue is resolved for us,
> we're don't mind specifying the options as part of the "from" string, but it
> seems an inconsistent/weird behavior between the two ways of declaring the
> options.
> *Original*:
> We are starting an AWS2-SQS route and enabling it every 30m using the
> controlbus component. We have set aws2-sqs concurrent consumers to 16. We
> have about 200 S3 events to the SQS queue every 10m.
> When we don't have the controlbus component route active, the AWS2 SQS route
> starts with 16 consumers and immediately (in a couple of seconds) consumes
> the entire queue even if we have thousands of events there. This was our
> default way of working until deciding to introduce a 30m wait between
> consumption.
> When we put the controlbus component performance degrades and consumption
> from SQS seems to be done via one thread (one consumer) taking minutes for
> just 200 events.
> We have the camel aws-sqs configuration in application.yml in Spring (as I
> write this, trying to put it on the "from" string).
> {code:java}
> camel:
> component:
> aws2-sqs:
> configuration:
> concurrent-consumers: 16
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
