Most of your questions are beyond my knowledge of NFS, so I'm not going to
be able to spot problems in your config or warn you about potential
problems. Maybe someone else can.
For NFSv3, the only concern I've heard about it in the context of ActiveMQ
is that its locking mechanisms don't allow it
Hi Tim,
Thanks for the reply. I had figured out the problem , it was due to options
used in mount which was causing issue .
I had used default options of timeo and retrans with Hard mode. After
changing the timeo and retrans with below values it started to work fine.
The broker was able to iden
I'm not an expert on NFS, but I'd have expected that the network
connectivity failure to the NFS share to be detected when the broker
attempts to read or write the file, not just when you disable connections
to it. Your description implies that you're doing the latter; what is the
behavior of the b
Hi,
In our activemq installation we are using kahaDb as the persistence adapter
with leased-database-locker for locking mechanism. The shared file system
used is NFSv3.
We wanted to test scenario where the Master node has access to mysql through
which it will remain master by acquiring lock but
