Kahadb with leased database locker broker not closing connector when connection to NFS fails.

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

Re: Kahadb with leased database locker broker not closing connector when connection to NFS fails.

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

Kahadb Activemq holds the lock but does start the broker service or connectors.

Hi, We had shared file locker with kaha db based persistence adapter in our 3 node master-slave-slave architecture. Master activemq was restarted couple of time and after a cycle or so it was seen that even though the activemq java process is up and it holds the lock it doesn't start the

Activemq: Kahadb persistence adapter with Leased-Database-locker for locking mechanism.

Hi, If we are using KahaDb as the persistence adapter the the default locker mechanism is shared file locker , with this we have restrictions on the shared file system that we use. The shared file system requires an efficient and reliable file locking mechanism . So if i am rite we should use