So something is very wrong then. NFS should *not* allow two NFS clients to obtain the same lock.
Three possible explanations come to mind: * The lock file is getting incorrectly removed (I've never seen ActiveMQ cause this) * There is a flaw in the NFS locking implementation itself * The NFSv4 timeout for the lock is overly aggressive (perhaps less than 1 second even? The timeout needs to be at least a couple of minutes in most scenarios to be reliable) If the servers are Linux servers, try using strace to see their interactions with the lock file. BTW, each broker is running on its own dedicated server, right? -- View this message in context: http://activemq.2283324.n4.nabble.com/question-for-users-of-NFS-master-slave-setups-tp4708204p4708644.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
