jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sascha Theves (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3155) Node not locked after upgrade to Jackrabbit 2.2.9
Date Fri, 25 Nov 2011 10:50:40 GMT

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

Sascha Theves commented on JCR-3155:

@Jukka Zitting: Thanks for the hint. Now I know where the problem comes from. We used in the
earlier version a db filesystem so that the locks were stored in the database. Now we are
using a normal filesystem and because of that the locks are gone.

So this issue here is not a bug of Jackrabbit. Please resolve as Won`t fix or just delete
the issue. Sorry for that and thx very much for your support!
> 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
> 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


View raw message