[
https://issues.apache.org/jira/browse/CAMEL-9592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149786#comment-15149786
]
Mary Cochran commented on CAMEL-9592:
-------------------------------------
I verified on the latest camel version that the maxMessagesPerPoll flag does
indeed need to be set when setting the concurrentConsumers for SQS to greater
than 1. I did manual test with routes and also adjust the unit test's route to
not set maxMessagesPerPoll. The unit test then failed with:
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.053 sec <<<
FAILURE! - in org.apache.camel.component.aws.sqs.SqsConcurrentConsumerTest
consumeMessagesFromQueue(org.apache.camel.component.aws.sqs.SqsConcurrentConsumerTest)
Time elapsed: 1.053 sec <<< FAILURE!
java.lang.AssertionError: We were expecting to have about half of 10 numbers of
concurrent consumers, but only found 1
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.camel.component.aws.sqs.SqsConcurrentConsumerTest.consumeMessagesFromQueue(SqsConcurrentConsumerTest.java:49)
I have filled out my ICLA and am waiting to get edit rights from the dev email
list. As soon as this is done I will make the documentation adjustment.
> Documentation on SQS ConcurrentConsumers Missing that you need to set
> maxMessagerPerPoll
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-9592
> URL: https://issues.apache.org/jira/browse/CAMEL-9592
> Project: Camel
> Issue Type: Bug
> Components: camel-aws
> Affects Versions: 2.15.1
> Reporter: Mary Cochran
> Labels: documentation
>
> If you try to use concurrentConsumers without setting the maxMessagesPerPoll
> whenever a message errors out it brings down the whole context.
> I plan on updating the wiki myself, but I haven't contributed before. I am
> going to start the process by emailing the dev list today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
