[
https://issues.apache.org/jira/browse/JCR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681667#action_12681667
]
Marius Ropotica edited comment on JCR-1634 at 3/13/09 6:58 AM:
---------------------------------------------------------------
I'm using jackrabbit 1.5 now , and this bug is not yet resolved. What is
happening? Why this bug is ignored? Did anyone found workarounds for this
problem?
This is the code that I'm trying to run in a transaction:
session.addLockToken(token);
Node node = session.getNodeByUUID(id);
node.unlock();
addLockToken method from SessionImpl delegates to method addLockToken from
XAEnvironment class. This method is empty.
was (Author: marius.ropotica):
Well, I'm using jackrabbit 1.5 now , and this bug is not yet resolved. What
is happening? Why this bug is ignored? Did anyone found workarounds for this
problem?
This is the code that I'm trying to run in a transaction:
session.addLockToken(token);
Node node = session.getNodeByUUID(id);
node.unlock();
addLockToken method from SessionImpl delegates to method addLockToken from
XAEnvironment class. This method is empty.
> In XA transaction session.addLockToken() does not have effect
> -------------------------------------------------------------
>
> Key: JCR-1634
> URL: https://issues.apache.org/jira/browse/JCR-1634
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, locks, transactions
> Affects Versions: core 1.4.4
> Environment: Jackrabbit Core 1.4.4, Jencks 2.0, Springmodules 0.8a,
> Jackrabbit JCA 1.4
> Reporter: Roman Puchkovskiy
> Attachments: test-external-lock-in-tx.zip
>
>
> Following sequence does not work as expected:
> 1. first tx (and first session)
> create node
> make it lockable
> 2. second tx (and second session)
> lock this node and save lock token
> 3. third tx (and third session)
> add saved lock token to session
> modify this locked node -> fails as if lock token was not added to session3
> The same sequence works as expected without transactions.
> I had to separate transactions 1 and 2 because JCR-1633 prevents node from
> being locked in same tx in which it was created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
