Hi Jason,
There are quite a few variables to consider for this, but from the top of my
head I'd suggest you look into increasing the "cache-level" and
"concurrentConsumers" properties of camel-jms and possibly provide pooling or
caching of your connections using something like Springs
"Caching
Hi,
Yes, broker mirroring sounds like a suitable solution to the use case you have
described, perhaps in particular "Dual Mirror" described here:
https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#dual-mirror-disaster-recovery
Personally I'd recomm
Sorry, but to my knowledge that is almost impossible to say for sure, as it's
highly dependent on your specific use case and setup. As before though, if you
can safely try it out, it might help in narrowing down the source of the issue.
I'd really like to reiterate that version upgrades to any p
Hi,
I think the point would be that if possible, the idea would be to try the same
conditions against a more recent version of the broker. All else being equal,
this would rule out any and all issues that might already have been addressed
in the roughly 3000 commits since 2.14.0. Same could app
