jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Przemo Pakulski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1979) Deadlock on concurrent read & transactional write operations
Date Fri, 13 Feb 2009 13:39:59 GMT

    [ https://issues.apache.org/jira/browse/JCR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673249#action_12673249
] 

Przemo Pakulski commented on JCR-1979:
--------------------------------------

Thread "http-8080-10" is executing readOnly operation, have acquired ReadLock for workspace
and is waiting on ReadLock for version storage.

Thread http-8080-18 is commiting transaction, have acquired WriteLock for version storage
already and waiting on WriteLock for workspace.

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