OK, digging into the code, here's how the keep-alive works with the
shared-filesystem-locker:
public boolean keepAlive() {
return lock != null && lock.isValid() && file.exists();
}
I suspect this code is either (a) ignoring the lost access to the server, or
(b) blocking. It should be possible to detect (b) by looking at the JVM
stack dump (e.g. using jstack).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problems-with-ActiveMQ-with-LevelDB-and-shared-filesystem-over-NFS4-tp4688074p4688356.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
