jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Puchkovskiy (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-1634) In XA transaction session.addLockToken() does not have effect
Date Fri, 30 May 2008 15:52:45 GMT
In XA transaction session.addLockToken() does not have effect

                 Key: JCR-1634
                 URL: https://issues.apache.org/jira/browse/JCR-1634
             Project: Jackrabbit
          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
            Reporter: Roman Puchkovskiy

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.

View raw message