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
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
Hi,
We do need XA as the client application is doing 2 phase commit in (1) the
subscription and (2) a database.
On Tue, Sep 3, 2019 at 14:49 Jean-Baptiste Onofré wrote:
> Hi,
>
> What about using pure ACK mode ?
>
> You can see an example with queue (same can be applied to topic) here:
>
Hi,
What about using pure ACK mode ?
You can see an example with queue (same can be applied to topic) here:
http://blog.nanthrax.net/?p=820
My point is: do you need XA as AFAIU you are using only JMS as resource
(XA is required when you want to use the same transaction with different
backends
