What version are you using? I might have some time to test this soon.
Justin On Wed, Feb 23, 2022 at 7:49 AM Gunawan, Rahman (GSFC-703.H)[Halvik Corp] <rahman.guna...@nasa.gov.invalid> wrote: > Correct, I can access the backup console so I would expect the same if the > primary becomes the backup. > > Thanks all for your help. > > Regards, > Rahman > > -----Original Message----- > From: Vilius Šumskas <vilius.sums...@rivile.lt> > 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 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 though. > > -- > Vilius > > -----Original Message----- > From: Justin Bertram <jbert...@apache.org> > 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 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:26 AM Gunawan, Rahman (GSFC-703.H)[Halvik Corp] < > rahman.guna...@nasa.gov.invalid> wrote: > > > 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 > > >
