Yup, I have tested by adding more than 5 messages and when I started the
route which Arnaud specified, it polled only one message at a time.
On Thu, Feb 3, 2022 at 9:23 AM Chirag wrote:
> Can you please post or point to a prototype ?
> Have you tried with putting large number if messages ?
>
> O
Can you please post or point to a prototype ?
Have you tried with putting large number if messages ?
On Wed, Feb 2, 2022, 17:35 Narsi Reddy Nallamilli <
narsi.nallami...@gmail.com> wrote:
> Hi Arnaud,
>
> Yup, It used to work before because I use it in my project and was not
> aware of the bug ti
Hi Arnaud,
Yup, It used to work before because I use it in my project and was not
aware of the bug till you reported.
Can you open up a jira for the same?
On Thu, 3 Feb, 2022, 01:00 Arnaud Level, wrote:
> Hi again Narsi,
>
> I read more about the *delay* component and you are right! Using it w
Hi again Narsi,
I read more about the *delay* component and you are right! Using it with a
custom (or even the default) thread pool profile we can have the expected
behavior without the thread pool being exhausted as I was thinking. This is
a workaround to the concurrentConsumer bug not being take
Hi Narsi,
Thank you for the reply! Indeed it works but not exactly as expected. I am
not sure to understand the behavior because with this delay it is not
limited to the number of concurrent consumers. If I set
concurrentConsumers=3 and I send 5 messages (which are read 1 by 1 with 5
pollings) I w
Hi Arnaud,
Yes, you are correct, 'concurrentConsumers; uri attribute is not working as
expected and this is some bug.
However I found when you use delay in the route it works as expected.
from("aws2-sqs://queuexxx?concurrentConsumers=5&amazonSQSClient=#sqsClient&
waitTimeSeconds=20")
.delay(1L)
Hi,
I have created one (my first 😉):
https://issues.apache.org/jira/browse/CAMEL-17588
Regards Björn
-Ursprüngliche Nachricht-
Von: Claus Ibsen
Gesendet: Mittwoch, 2. Februar 2022 14:34
An: users@camel.apache.org
Betreff: Re: ThreadLocal
org.apache.camel.impl.engine.DefaultReactiveEx
Hi
Yeah we should cleanup this, you are welcome to create a JIRA
On Wed, Feb 2, 2022 at 2:07 PM Björn Ohm wrote:
>
> Hi,
>
> we have migrate from 2.x to 3.14.1 in our test-environment. We are running
> our Camel-Application on a Tomcat (Provide soap-services over CXF-Endpoint,
> route Messages
Hi,
we have migrate from 2.x to 3.14.1 in our test-environment. We are running our
Camel-Application on a Tomcat (Provide soap-services over CXF-Endpoint, route
Messages in JMS-Queues, read from JMS-Queue with JMS-Endpoint, an then do other
things...)
While the Tomcat-Shutdown we observed a bu
