You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Jorge Rodríguez Pedrianes (JIRA)" <ji...@apache.org> on 2008/06/09 16:25:45 UTC

[jira] Commented: (JCR-1173) Session scoped lock has no effect on other cluster nodes

    [ https://issues.apache.org/jira/browse/JCR-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603574#action_12603574 ] 

Jorge Rodríguez Pedrianes commented on JCR-1173:
------------------------------------------------

Hello!!,

I`m very interesting in this issue because it's very important to my applications.

A solution is based to use JGroups (http://www.jgroups.org/)  that allow to lock resources (LockManager class).

This is an idea,

Thanks

> Session scoped lock has no effect on other cluster nodes
> --------------------------------------------------------
>
>                 Key: JCR-1173
>                 URL: https://issues.apache.org/jira/browse/JCR-1173
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: clustering
>    Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.3
>            Reporter: Michael Frericks
>
> javax.jcr.Node#lock(..., true) locks the node only in this cluster node.
> On any other node of the cluster you can access and change the same node concurrently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.