t; > Hi JB,
> >
> > I think the timeout is too long and Kubernetes kills the pod. What is
> the location of the lock file?
> >
> > Cheers,
> >
> >Fabrice
> >
> >
> > From: Jean-Baptiste Onofré
> >
brice
From: Jean-Baptiste Onofré
Sent: 10 August 2021 18:04
To: users@activemq.apache.org
Subject: Re: How to disable KahaDB lock?
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sende
Hi JB,
I think the timeout is too long and Kubernetes kills the pod. What is the
location of the lock file?
Cheers,
Fabrice
From: Jean-Baptiste Onofré
Sent: 10 August 2021 18:04
To: users@activemq.apache.org
Subject: Re: How to disable KahaDB lock
You can take a look on my blog post "Apache ActiveMQ 5.7, 5.9 and
Master-Slave" for some details.
Regards
JB
The lease locker would work only for JDBC store.
However you can mix both (see my blog post about that).
Regards
JB
et me know how to do that?
Thanks,
Fabrice
From: JB Onofré
Sent: 10 August 2021 16:53
To: users@activemq.apache.org
Subject: Re: How to disable KahaDB lock?
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments
When it is subsequently restarted, it must work.
Could you please let me know how to do that?
Thanks,
Fabrice
From: JB Onofré
Sent: 10 August 2021 16:53
To: users@activemq.apache.org
Subject: Re: How to disable KahaDB lock?
CAUTION: This email originated from
t;
Datum: 10.08.2021 17:47
Betreff: How to disable KahaDB lock?
Hi everyone,
It seems that when ActiveMQ terminates uncleanly, it leaves a lock on the
Kaha DB. Next time it starts, it complains that the DB is locked and goes
in slave mode.
In my setup, I am 100% certain that a given b
Hi
No as soon as a broker start with kahadb it lock kahadb.
Imho you have a file system issue or config: I never had locking issue with
kahadb.
You can always remove the lock manually but I would check if you don’t have
another process or so.
Regards
JB
> Le 10 août 2021 à 17:46, Fabric
Hi everyone,
It seems that when ActiveMQ terminates uncleanly, it leaves a lock on the Kaha
DB. Next time it starts, it complains that the DB is locked and goes in slave
mode.
In my setup, I am 100% certain that a given broker will access one and only one
KahaDB, so I would like to configure A
10 matches
Mail list logo
