jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rod Mackenzie (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-546) Deadlock during checkin
Date Mon, 21 Aug 2006 10:59:13 GMT
Deadlock during checkin 

                 Key: JCR-546
                 URL: http://issues.apache.org/jira/browse/JCR-546
             Project: Jackrabbit
          Issue Type: Bug
          Components: versioning
         Environment: WinXP Jackrabbit r431916
            Reporter: Rod Mackenzie
            Priority: Critical

Under a load of 3 threads performing checkin and restore operations it's possible for all
to become deadlocked in AbstractVersionManager.checkin(). This method attempts to upgrade
a read lock to a write lock with the following code


    try {

If 2 or more threads acquire the read lock then neither can acquire the write lock resulting
in the deadlock, and after that any other thread that calls this method will block waiting
for the write lock. The release of the read lock needs to be done before acquiring the write
lock, this is documented Concurrent library javadoc.

There is another area where there is an attempt to upgrade a read lock to write lock, RepositoryImpl.WorkspaceInfo.disposeIfIdle()
acquires a read lock and calls dispose() which then acquires a write lock, this maybe ok,
as I assume there is only 1 thread that will attempt to dispose of idle workspaces.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message