gt; I'm using Artemis version 2.19.1. Thanks for your help.
>
> Rahman
>
> -Original Message-
> From: Justin Bertram
> Sent: Wednesday, February 23, 2022 8:57 AM
> To: users@activemq.apache.org
> Subject: Re: [EXTERNAL] RE: Artemis share store config allow-f
I'm using Artemis version 2.19.1. Thanks for your help.
Rahman
-Original Message-
From: Justin Bertram
Sent: Wednesday, February 23, 2022 8:57 AM
To: users@activemq.apache.org
Subject: Re: [EXTERNAL] RE: Artemis share store config allow-failback= false
question
What version ar
or your help.
>
> Regards,
> Rahman
>
> -Original Message-
> From: Vilius Šumskas
> Sent: Tuesday, February 22, 2022 5:15 PM
> To: users@activemq.apache.org
> Subject: [EXTERNAL] RE: Artemis share store config allow-failback= false
> question
>
> At l
: Artemis share store config allow-failback= false
question
At least under normal circumstances backup should be accessible via console. I
just checked on my shared storage cluster. It even shows cluster diagram
(without consumers and producers).
Didn't try with allow-failback set to false t
ustin Bertram
Sent: Tuesday, February 22, 2022 11:54 PM
To: users@activemq.apache.org
Subject: Re: Artemis share store config allow-failback= false question
I believe that is the expected behavior. The broker is not operational while it
is waiting for the lock which is kind of the whole
I believe that is the expected behavior. The broker is not operational
while it is waiting for the lock which is kind of the whole point.
Therefore, I think the embedded web server won't be operational and there
won't be any of the broker's JMX objects available.
Justin
On Tue, Feb 22, 2022 at 9
If I set "allow-failback" = false in backup server, the primary was announced
as backup and waiting for the lock when it recovered from crash. However; I
couldn't login to the primary Artemis UI console. Is it normal?
Thanks
Regards,
Rahman
