Jackrabbit Content Repository
  1. Jackrabbit Content Repository
  2. JCR-2855

Writers blocked forever when waiting on update operations

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.3, 2.2.1
    • Fix Version/s: 2.2.4
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      Thread 1 calls Session.save() and has a write lock.

      Thread 2 is in XA prepare() and is waiting on thread 1 in FineGrainedISMLocking.acquireWriteLock().

      Thread 1's save calls SharedItemStateManager.Update#end() and performs a write-lock downgrade to a read-lock, then (at the end of Update#end()) it calls readLock.release(). FineGrainedISMLocking.ReadLockImpl#release thinks activeWriterId is of the current transation and does not notify any writers (activeWriterId is not being reset on downgrade in what seems to be a related to JCR-2753).
      Thread 1 waits forever.

        Activity

          People

          • Assignee:
            Jukka Zitting
            Reporter:
            Yoav Landman
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development