binary identical to same file on primary server0. So, problem seems
persisting the headers in journal on backup broker.
Kind regards,
Arno
Von: Arno Schuerhoff
Gesendet: Montag, 29. April 2024 09:09
An: users@activemq.apache.org
Betreff: AW: Suspected slow replication
Hello Justin, I have created
@activemq.apache.org
Betreff: Re: Suspected slow replication
I'm not aware of anything related to reloading broker. xml that would impact
replication, and I don't think replication itself will change the size of the
message (e. g. via adding headers). Replication is performed at the journal
level s
sender of that messages, but only information is
> time point and size of application properies.
>
> Is there any option to get more log output from live or backup broker to
> get more message properties like queue name?
>
> Kind regards,
> Arno
>
>
>
> Von: Arno Schuer
output from live or backup broker to get
more message properties like queue name?
Kind regards,
Arno
Von: Arno Schuerhoff
Gesendet: Dienstag, 23. April 2024 13:54
An: users@activemq.apache.org
Betreff: Suspected slow replication
Hello all, we are using Artemis MQ in a fail-safe configuration
Hello all,
we are using Artemis MQ in a fail-safe configuration with active primary broker
and replicating backup.
This works since years and many thanks for this great application.
Some weeks ago, we have replaced old broker pair by a fresh installation using
Artemis MQ version 2.31.2.
Startin
