[JCR-1634] In XA transaction session.addLockToken() does not have effect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: core 1.4.4
• Fix Version/s: 1.6
• Component/s: jackrabbit-core
• Environment: Jackrabbit Core 1.4.4, Jencks 2.0, Springmodules 0.8a, Jackrabbit JCA 1.4
• Assignee: Claus Köll
• Reporter: Roman Puchkovskiy
• Created: 30/May/08 15:51
• Updated: 13/Aug/09 15:03
• Resolved: 20/May/09 16:59

Description

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.