Ah this is mostly unrelated to that other issue, I just figured I should mention it as it did give me momentary trouble at some point in my own implementation. That other issue still persists and at this time I still haven't found any information related to it.
-----Original Message----- From: Justin Bertram <jbert...@apache.org> Sent: Friday, February 21, 2025 4:38 PM To: users@activemq.apache.org Subject: Re: allow-failback document wrong EXTERNAL EMAIL - Proceed with Caution! Think carefully before you click on a link, open an attachment, or scan a QR code. NEVER provide User IDs or Passwords. Report any suspicious emails using the Phish Alert Button. [You don't often get email from jbert...@apache.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] A quick look indicates the doc needs to be updated. However, the Stack Overflow question you cited has a snippet from broker.xml where allow-failback is set to true. Does that snippet not reflect what you were actually testing with? Justin On Fri, Feb 21, 2025 at 3:43 PM Sergio Scaramuzzi <sergio.scaramu...@richardson.ca.invalid> wrote: > Hello, > > I think I've discovered a problem with the latest documentation for HA. > https://protect.checkpoint.com/v2/r03/___https://activemq.apache.org/c > omponents/artemis/documentation/latest/ha.html%23replication___.YzFjOn > JpY2hhcmRzb25pbnRlcm5hdGlvbmFsOmM6bzpmYjZmZjJiZWViMWIzM2FmN2VjZjMxOTdj > NjE4NGJjMjo3OjBkMGE6ZTkyN2FkYmQ3OGYyMTMwMzVmYmI1ZDEzMTQyODg4ZjFhNjNkZj > VjYmQ4OGY0YmYzZWIzMDc0NDJmM2RmYTMzNjpwOlQ6Tg > > It claims that allow-failback is true by default but in my > experiments, I've found my primary brokers do not resume control > unless I explicitly declare allow-failback as true in my broker.xml, > which then results in the expected behavior. > > I could be terrible mistaken about this but at least that's what seems > to be occurring for me on both 2.38.0 and 2.39.0. > This may not even be the right channel for this but figured you guys > may want to know/check in on this! > > Thanks, > Sergio Scaramuzzi > > > > > > The foregoing message, together with any attachments is intended for > the addressee only. If you believe you received this message in > error, please delete all copies of this message. If you no longer > wish to receive electronic messages, please reply to this message with > the word "UNSUBSCRIBE" in the subject line and you will be removed > from our mailing lists. Thank you. > The foregoing message, together with any attachments is intended for the addressee only. If you believe you received this message in error, please delete all copies of this message. If you no longer wish to receive electronic messages, please reply to this message with the word "UNSUBSCRIBE" in the subject line and you will be removed from our mailing lists. Thank you.