[
https://issues.apache.org/jira/browse/JCR-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674593#action_12674593
]
Thomas Mueller commented on JCR-1605:
-------------------------------------
Committed in revision 745500 (repository-1.6.dtd changes)
> RepositoryLock does not work on NFS sometimes
> ---------------------------------------------
>
> Key: JCR-1605
> URL: https://issues.apache.org/jira/browse/JCR-1605
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: repositoryLockMechanism.patch
>
>
> 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.
