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

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/01/08 12:58:59 UTC

[jira] Resolved: (JCR-1875) Failing Node.unlock() might leave inconsistent transient state

     [ https://issues.apache.org/jira/browse/JCR-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved JCR-1875.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0
         Assignee: angela

> Failing Node.unlock() might leave inconsistent transient state
> --------------------------------------------------------------
>
>                 Key: JCR-1875
>                 URL: https://issues.apache.org/jira/browse/JCR-1875
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, locks
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.6.0
>
>
> Similar to issue JCR-538 but for Node.unlock():
> If updating the lock related properties (jcr:lockIsDeep or jcr:lockOwner) fails e.g. due to missing permission, there might be inconsistent transient modifications pending.

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