jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1979) Deadlock on concurrent read & transactional write operations
Date Mon, 16 Feb 2009 13:53:04 GMT

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

Jukka Zitting resolved JCR-1979.
--------------------------------

    Resolution: Fixed

Merged to the 1.5 branch in revision 744916.

I've scheduled a massively parallel randomized test run (now including getReferences() calls
on version nodes) for tonight. Przemo, can you check the fix on your side and perhaps run
some of your test cases on it?

> Deadlock  on concurrent read & transactional write operations
> -------------------------------------------------------------
>
>                 Key: JCR-1979
>                 URL: https://issues.apache.org/jira/browse/JCR-1979
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.5.0
>            Reporter: Przemo Pakulski
>            Assignee: Jukka Zitting
>             Fix For: 1.5.3
>
>
> Isuue has been introduced by resolving JCR-1755 (Transaction-safe versioning). This fixed
changed sequence of commits, but at the same time order of acquiring locks has been disturbed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message