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 <shenr...@smartwavesa.com> wrote: > 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 a custom executor service would improve performance as > it seems that the main thread is competing with the Aggregator threads. > > Thanks > Sydney -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
