>From the logs provided by the AWS support, I can see these 2 issues:
1) Sometimes Camel doesn't set the visibilityTimeout(or Camel sends the
request but AWS doesn't set it) and Camel doesn't catch this information.
2) Sometimes AWS fails to extend the visibilityTimeout and Camel catch it.
Camel th
Hi,
Thank you for your reply. I don't have a simple reproducer. It happens
about once in 200 messages. It is rare but it does happen almost everyday.
That's quite annoying :(
On 01/07/2019, 14:46, "Andrea Cosentino"
wrote:
>Do you have a simple reproducer for this?
>
>--
>Andrea Cosentino
>
Do you have a simple reproducer for this?
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, June 25, 2019, 5:11:05 PM GMT+2, Qingyang Xu
Hi,
We have a micro service (multiple instances and each instance has multiple
consumers) on AWS that uses Camel aws-sqs to listen to a AWS sqs queue.
Our camel version is 2.24.0 and the aws-sqs config is
visibilityTimeout=300&extendMessageVisibility=true&maxMessagesPerPoll=5&con
currentConsumers=5