[
https://issues.apache.org/jira/browse/JCR-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619504#action_12619504
]
Claus Köll commented on JCR-1702:
---------------------------------
a little bit more debugging :-)
on operations like NodeImpl.addNode() or save()
the XASession from the loggend in user will be used and so the
CachingHierarchyManager from this session.
on other methods like NodeImpl.checkLock() or lock() (they are coming through
the XAEnvironment)
the SystemSession will be used and so the CachingHierarchyManager from this
session
that was not be informed about the new added node !
its a little bit hard to explain :-)
if you are looking into the XALockManager lock() method that uses the
XAEnvironment to lock the node,
and this XAEnvironment uses its LockManager to get the Path of the new added
Node but it uses
the SystemSession that holds the not informed CachingHierarchyManager .
Hope for help !
claus
> Unable to create/lock Node in one Transaction
> ---------------------------------------------
>
> Key: JCR-1702
> URL: https://issues.apache.org/jira/browse/JCR-1702
> Project: Jackrabbit
> Issue Type: Bug
> Components: transactions
> Affects Versions: core 1.4.5
> Reporter: Claus Köll
>
> If i try to add a node and then add a lock on it inside one transaction i get
> a exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
