- Posted In
- Red Hat JBoss AMQ
We are having a problem on Fuse-AMQ 6.3.0 424 R14 (and 377 R11) with a NFS master/slave configuration. Sometimes, when we restart the slave fuse-amq broker it steal the lock and becomes master, stopping the previous master.
This happens occasionally... Can it be a NFS server configuration issue?
We have defined the following properties in the kahaDB persistence adapter:
and in the shared-file-locker:
Any other settings to consider?