Hi Larry,
Thank you for your message! Your reply makes sense to me and I've tried
what you suggested to test it with a queue like:
from("aws2-sqs://aramark-notifications?maxMessagesPerPoll=1=5=#sqsClient")
but it does not change, I still see the messages with a delay of 5 seconds
between each of
Hi Arnaud,
I think what may be happening is that you first consumer is grabbing all of
the messages from the queue that are available. The default message poll
size is unlimited so your other 4 consumers are polling for nothing on the
queue. What you might want to try is setting the
Hi Narsi,
It's a fifo but I actually tried the simple code I've posted on a standard
one too and observed the same behavior.
On Mon, Jan 31, 2022 at 1:11 PM Narsi Reddy Nallamilli <
narsi.nallami...@gmail.com> wrote:
> Hi Arnaud,
>
> Is your AWS queue type fifo or standard?
>
> On Mon, 31 Jan,
Hi Arnaud,
Is your AWS queue type fifo or standard?
On Mon, 31 Jan, 2022, 17:31 Arnaud Level, wrote:
> Hi,
>
> (Camel version: camel-aws2-sqs-starter: 3.12.0)
>
> I am trying to use and understand concurentConsumers with a SQS queue:
>
>
Hi,
(Camel version: camel-aws2-sqs-starter: 3.12.0)
I am trying to use and understand concurentConsumers with a SQS queue:
from("aws2-sqs://queuexxx?concurrentConsumers=5=#sqsClient&
waitTimeSeconds=20")
.process(exchange -> {
System.out.println("Message
Hi,
I had a look and the CLI indeeds return 0 when trait properties validation
fails, whether the property is passed with the -t option or with modeline.
It should be fixed with https://github.com/apache/camel-k/pull/2964
Thanks a lot for reporting the issue.
Antonin
On 28 Jan 2022, at
