Hi
You can try setting asyncConsumer=true on JMS endpoint which allows it to
consume messages out-of-order. See the docs for more details.
On Sun, Sep 4, 2022 at 4:55 PM Sydney Henrard
wrote:
> Hello,
>
> The unit test is using the latest version 3.18.1.
>
> I did not really get your point on
Hello,
The unit test is using the latest version 3.18.1.
I did not really get your point on using LevelDB as the unit test reproduces
the issue without persistence. The aggregation is used to remove duplicates
from 25 millions messages, knowing that there are 600K unique ids.
I wonder if using
Hi
This sounds like a not so good design with using leveldb as a temporary
storage.
Instead I would look at designing so you can aggregate in smaller batches
and send back to the JMS broker, and have 2nd routes consume from that to
continue routing.
What Camel version do you use?
On Sat, Sep
Hello,
In my application I have a route that consumes a JMS queue, then aggregate on a
header and finally process. The issue is that the consumption of the queue is
stopped until the processing is done. The queue contains 25 millions messages
(600K unique messages based on aggregation rule), ag
