The cache shouldn’t be enabled, as we are using XA (as per Camel’s
recommendation). We have also tuned the polling interval.
That being said, what hurts the I/O subsystem on the MQ server is the
Subscribe operation itself (not the polling for messages).
I am wondering is if there would be any way
camel-jms uses spring jms, so there are many users with this combo
also with IBM MQ and XA.
Look at the many options spring jms has to tune its polling, and also
cache levels you can tweak.
There may be some more idle options you can set to make it "sleep"
longer when there are no messages.
But you
Thanks a lot Zoran
Il mer 4 set 2019, 10:24 Zoran Regvart ha scritto:
> Hi Knut-Håvard,
> thank you for noticing that, it's one of those things when you look at
> a it and over time it seems more right than wrong so you don't notice
> the wrong any more.
>
> I've pushed a fix for this[1][2], and
Hi Knut-Håvard,
thank you for noticing that, it's one of those things when you look at
a it and over time it seems more right than wrong so you don't notice
the wrong any more.
I've pushed a fix for this[1][2], and it's now live.
As a reminder to the rest of the community, now that we have the
we
