You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Gunawan, Rahman (GSFC-703.H)[Halvik Corp]" <ra...@nasa.gov.INVALID> on 2022/02/22 15:25:18 UTC
Artemis share store config allow-failback= false question
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
Re: [EXTERNAL] RE: Artemis share store config allow-failback= false question
Posted by Justin Bertram <jb...@apache.org>.
At this point I'd say you're seeing the expected behavior. A broker
configured as a master which is unable to acquire the shared-store lock and
activate will not deploy the embedded web server.
Justin
On Wed, Feb 23, 2022 at 8:46 AM Gunawan, Rahman (GSFC-703.H)[Halvik Corp]
<ra...@nasa.gov.invalid> wrote:
> I'm using Artemis version 2.19.1. Thanks for your help.
>
> Rahman
>
> -----Original Message-----
> From: Justin Bertram <jb...@apache.org>
> 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 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.gunawan@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 <vi...@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 <jb...@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.gunawan@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
> > >
> >
>
RE: [EXTERNAL] RE: Artemis share store config allow-failback= false question
Posted by "Gunawan, Rahman (GSFC-703.H)[Halvik Corp]" <ra...@nasa.gov.INVALID>.
I'm using Artemis version 2.19.1. Thanks for your help.
Rahman
-----Original Message-----
From: Justin Bertram <jb...@apache.org>
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 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] <ra...@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 <vi...@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 <jb...@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.gunawan@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
> >
>
Re: [EXTERNAL] RE: Artemis share store config allow-failback= false question
Posted by Justin Bertram <jb...@apache.org>.
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]
<ra...@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 <vi...@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 <jb...@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.gunawan@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
> >
>
RE: [EXTERNAL] RE: Artemis share store config allow-failback= false question
Posted by "Gunawan, Rahman (GSFC-703.H)[Halvik Corp]" <ra...@nasa.gov.INVALID>.
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 <vi...@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 <jb...@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] <ra...@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
>
RE: Artemis share store config allow-failback= false question
Posted by Vilius Šumskas <vi...@rivile.lt>.
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 <jb...@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] <ra...@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
>
Re: Artemis share store config allow-failback= false question
Posted by Justin Bertram <jb...@apache.org>.
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]
<ra...@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
>