Never mind, we figured it out. Turns out mirroring is configured on the broker
side since RabbitMQ 3.0 (:facepalm).
Once the primary went down Camel couldn't do anything with the in-flight
messages anymore since the queues were not mirrored on the secondary vm. So the
below is probably a very ex
Hi All,
Hopefully someone can help me out here. In the project I'm working on we're
using the camel-rabbitmq component to connect to a cluster of three RabbitMQ
nodes. We're using the addresses parameter in the URL configuration of the
RabbitMQ facing endpoints, like this:
from:rabbitmq://vmsy
Hi Zoran,
Thank you for the help and your reply. I figured it out later at some point
this was the way to go about and got my problem resolved.
I used the queryMore and nextRecordUrl methods on my
AbstractQueryRecordBase.
Cheers
Dicken
On Fri, Sep 21, 2018 at 3:11 PM Zoran Regvart wrote:
> `H
