A follow on question:
When are messages ACKed in this scenario?
Is the ACK to the producer only sent when the message has been persisted to
both original and diverted to queues/addresses?
Scenario:
You have simple/normal: request/response queues for clients.
For DR (Disaster Recovery) purposes it is required to backup each queue's
messages for 1 month.
(And this is required to be done on the broker itself in
backup-request/backup-response queues.)
This way if clients lose their me
I'm referring to the Artemis User Manual p.324
Does this duplicate detection work with the AMQP protocol?
If so: is it the same property field that has to be set: _AMQ_DUPL_ID? (why not
just use the message-ID?)
Where does this property value have to be set in the AMQP message?
>>> Technically speaking, replication is asynchronous. However, the broker
will not send a response to the client until it has received a reply from
the slave that the data has been received.
...
>>> If the network between the master and slave goes down then by default
>>> the master continues like
I have a very similar scenario to the original post. (Multi data center
replication is required)
I have read all the documentation -- but am unclear about a couple of
points:
1) RedHat AMQ 7 (which is using Artemis under the hood) in their
"configuring broker" documentation recommend NOT using [HA
