[
https://issues.apache.org/jira/browse/AMQ-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957010#comment-14957010
]
ASF subversion and git services commented on AMQ-4705:
------------------------------------------------------
Commit b285d1018803ceb4fdf7ea14c178de1e0abc9c8a in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=b285d10 ]
https://issues.apache.org/jira/browse/AMQ-4705 - ensure jvm lock system
property is cleared in the event of lock release throwing exception.
> Add keep alive support to shared file locker
> --------------------------------------------
>
> Key: AMQ-4705
> URL: https://issues.apache.org/jira/browse/AMQ-4705
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.8.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: kahadb, netapp, nfsv4, shared-file-lock
> Fix For: 5.12.0
>
> Attachments: AMQ-4705-GMURTHY-PATCH.TXT, KahaDBDeleteLockTest.java
>
>
> issue on nsfv4 with a master slave configuration, where both the slave and
> the master could obtain a lock.
> The following events occurred:
> * master locks the file - does no more i/o to it – it's passive wrt the lock
> * slave asks every 10 seconds if it can get the lock nfs come back and say
> no, someone has it
> * nfs dies not nicely
> ** nfsv4 is stateful - no callback for locks.
> ** It has a grace period of 30 seconds to let all clients that had locks
> reclaim them as locked
> * master does not realize it needs to reclaim the lock and continues under
> the assumption it has the lock.
> * After 30 sec grace period, slave comes in and asks for the lock and it
> receives it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
