[
https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156818#comment-13156818
]
Jukka Zitting commented on JCR-3155:
------------------------------------
In revision 1205925 I added a simple backwards compatibility test that verifies
that open-scoped should survive an upgrade from any previous Jackrabbit version
(starting wth 1.0). The test passes without problems, so I assume your problem
is somehow specific to your repository instance.
> Maybe you could give me a hint or something where to investigate further...
The set of active open-scoped locks are stored in a "locks" file within each
workspace directory, one lock token per line. Check that this file exists in
your repository and that it contains the UUID of the node that should be locked.
> Node not locked after upgrade to Jackrabbit 2.2.9
> -------------------------------------------------
>
> Key: JCR-3155
> URL: https://issues.apache.org/jira/browse/JCR-3155
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.2.9
> Reporter: Sascha Theves
> Fix For: 2.2.10
>
>
> Lock a node in Jackrabbit 1.6.2 with node.lock(true, false). That is a deep
> lock, not session-scoped.
> Then upgrade to Jackrabbit 2.2.9 and check the node with node.isLocked.
> Now node.isLocked() returns false (wrong!) and
> node.getProperty("jcr:lockOwner") is set. That is an inconsistent node state.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
