Hi Rahman- High likelihood that the Artemis server's NFSv3 services did not release the lock when the connectivity to the NFS server went away.
This sounds like the exact use case as to why NFSv4 is generally recommended these days. -Matt Pavlovich > On Feb 28, 2022, at 11:24 AM, Gunawan, Rahman (GSFC-703.H)[Halvik Corp] > <rahman.guna...@nasa.gov.INVALID> wrote: > > I'm using NFS v3. What is the recommended version? I don't see the minimum > NFS requirement in > https://activemq.apache.org/components/artemis/documentation/2.19.0/ha.html. > > Thanks > > Rahman > > -----Original Message----- > From: Vilius Šumskas <vilius.sums...@rivile.lt> > Sent: Monday, February 28, 2022 8:57 AM > To: users@activemq.apache.org > Subject: RE: [EXTERNAL] Re: Artemis file locking not released > > Are you using NFS version 4.1 and what's are your mount options? > > -- > Vilius > > -----Original Message----- > From: Gunawan, Rahman (GSFC-703.H)[Halvik Corp] > <rahman.guna...@nasa.gov.INVALID> > Sent: Monday, February 28, 2022 2:55 PM > To: users@activemq.apache.org > Subject: RE: [EXTERNAL] Re: Artemis file locking not released > > The backup server knew that the primary server had problem. Below is from > the log from the backup server: > ERROR [org.apache.activemq.artemis.core.client] AMQ214016: Failed to create > netty connection: java.net.UnknownHostException > > Thus, I'm thinking if the Artemis primary server lost connection to NFS or > network, the backup server can detect, unlock the file and take over. Please > let me know if you have suggestions. > Thanks > > Regards, > Rahman > > -----Original Message----- > From: Clebert Suconic <clebert.suco...@gmail.com> > Sent: Saturday, February 26, 2022 9:27 AM > To: users@activemq.apache.org > Subject: [EXTERNAL] Re: Artemis file locking not released > > Could be some configuration on the remote file system attributes ? > > On Fri, Feb 25, 2022 at 12:03 PM Gunawan, Rahman (GSFC-703.H)[Halvik Corp] > <rahman.guna...@nasa.gov.invalid> wrote: > >> I'm using Artemis 2.19.1. I'm using share file configuration and >> testing a scenario where the primary Artemis server is isolated from >> the network by disabling the network card. Because the primary server >> lost communication to NFS, the file is never unlock and the backup >> server is always waiting for the lock. When we enable the network >> card in primary server, the primary server is completely down. Below is the >> primary server log: >> "Reference Handler" Id=2 WAITING on java.lang.ref.Reference$Lock@64b6b3fc >> at java.lang.Object.wait(Native Method) >> - waiting on java.lang.ref.Reference$Lock@64b6b3fc >> at java.lang.Object.wait(Object.java:502) >> at java.lang.ref.Reference.tryHandlePending(Reference.java:191) >> at >> java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153) >> >> >> >> ====================================================================== >> ========= >> End Thread dump >> >> Is this bugs in Artemis share file configuration? >> >> Regards, >> Rahman >> > -- > Clebert Suconic
