[
https://issues.apache.org/jira/browse/JCR-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877107#action_12877107
]
Claus Köll commented on JCR-2341:
---------------------------------
The Problem is that the LockManagerImpl uses the NodeState of the
ItemStateManager to remove the Property lockOwner on unlock() operation.
On Node.remove() the internal NodeState will be used where the Property is
already present.
> Unable to add/lock and unlock/remove Node with shared Session in 2
> Transactions
> -------------------------------------------------------------------------------
>
> Key: JCR-2341
> URL: https://issues.apache.org/jira/browse/JCR-2341
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.6.0
> Reporter: Claus Köll
> Assignee: Claus Köll
> Attachments: JCR-2341.patch
>
>
> If you try to unlock and remove a node the NodeState can be run out of sync
> between the two operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
