For what it's worth, the broker is pretty much at the mercy of the filesystem here. The broker attempts to acquire a file lock using standard Java file APIs. If the filesystem allows those API calls to complete normally (i.e. without throwing an exception) then the broker must assume they were successful. It has no way of knowing whether or not the filesystem has actually implemented the proper locking mechanism.
Justin On Tue, Jun 18, 2019 at 5:42 AM hannibal <hanniba...@gmail.com> wrote: > Failover issues were due to inability to take the lock on the filesystem. > Moving to an external NFSv4 solved the problem. > Unfortunately, from logs this is not immediate. Actually, the backup server > says that it acquires the backup lock even if this is not true. > > Thanks for help. > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
