You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Przemo Pakulski (JIRA)" <ji...@apache.org> on 2009/02/13 14:39:59 UTC
[jira] Issue Comment Edited: (JCR-1979) Deadlock on concurrent
read & transactional write operations
[ https://issues.apache.org/jira/browse/JCR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673249#action_12673249 ]
ppakulski edited comment on JCR-1979 at 2/13/09 5:38 AM:
---------------------------------------------------------------
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.
was (Author: ppakulski):
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.