[
https://issues.apache.org/jira/browse/JCR-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597165#action_12597165 ]
Julian Reschke commented on JCR-1605:
-------------------------------------
Does this need to be configurable? Wouldn't it be sufficient to catch the Exception and then fall back to the new approach?
> RepositoryLock does not work on NFS sometimes
> ---------------------------------------------
>
> Key: JCR-1605
> URL:
https://issues.apache.org/jira/browse/JCR-1605> Project: Jackrabbit
> Issue Type: Bug
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
>
> The RepositoryLock mechanism currently used in Jackrabbit uses FileLock. This doesn't work on some NFS file system. It looks like only NFS version 4 and newer supports locking. Older implementations may throw a IOException "No locks available", which means the NFS does not support byte-range locking.
> I propose to add a second locking mechanism, and add a configuration option to use it. For example: <FileLocking class="acme" />. This second locking mechanism is a cooperative locking protocol that uses a background (watchdog) thread and only uses regular file operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
