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

["Roman Puchkovskiy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Puchkovskiy updated JCR-1634:
-----------------------------------

    Attachment: test-external-lock-in-tx.zip

Attaching test case. It contains two test methods: one without transactions, another using transactions.

> 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 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.