You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Sascha Theves (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 10:29:40 UTC
[jira] [Created] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156696#comment-13156696 ]
Sascha Theves commented on JCR-3155:
------------------------------------
@Claus: I did nothing special. Started Jackrabbit 1.6.2, created some nodes, locked a node and stoped Jackrabbit. Afterwards I started Jackrabbit 2.2.9 and used the same workspace. Maybe the Jackrabbit versions are important. I never tried it with a 2.4.0 SNAPSHOT.
> 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
[jira] [Resolved] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sascha Theves resolved JCR-3155.
--------------------------------
Resolution: Invalid
> 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155765#comment-13155765 ]
Sascha Theves commented on JCR-3155:
------------------------------------
Any patches are appreciated.
> 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Commented) (JIRA)" <ji...@apache.org>.
[ 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 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
[jira] [Closed] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Jukka Zitting (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting closed JCR-3155.
------------------------------
No worries, good that the problem got solved!
> 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156790#comment-13156790 ]
Sascha Theves commented on JCR-3155:
------------------------------------
I cannot reproduce the problem in a simple JUnit test but I can reproduce it every time with one of our "old" databases... I really don`t know what exactly causes the problem. For me it looks like the simple update to Jackrabbit 2.2.9 was the reason and it must have something to do with that... Maybe you could give me a hint or something where to investigate further...
> 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Claus Köll (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156681#comment-13156681 ]
Claus Köll commented on JCR-3155:
---------------------------------
How did you made the upgrade ?
I have created a node with jackrabbit 1.6 and locked it.
Now i have opened the workspace with the current jackrabbit 2.4.0-SNAPSHOT and the node was also locked .
greets
claus
> 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
[jira] [Commented] (JCR-3155) Node not locked after upgrade to
Jackrabbit 2.2.9
Posted by "Sascha Theves (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157095#comment-13157095 ]
Sascha Theves commented on JCR-3155:
------------------------------------
Yes, agree ;)
> 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