Uploaded image for project: 'Hippo Repository'
  1. Hippo Repository
  2. REPO-1645

Patched Jackrabbit LockManagerImpl is not fully honoring the JCR API

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Labels:
      None
    • Similar issues:
    • Story Points:
      1
    • Processed by team:
      Platform
    • Sprint:
      Platform Sprint 153

      Description

      REPO-1381 intruced a new 'lazy' or 'just-in-time' expiration handling of JCR locks, thereby no longer needing the Jackrabbit default background thread monitoring and removing possibly expired locks.

      However, that customization currently does not honor a few JCR Lock API method usages: #isLive() and #getSecondsRemaining(), and which actually fail when running the Jackrabbit integration tests.

      Furthermore the internal (within LockManagerImpl) boolean #unlockIfExpired(LockInfo) method is incorrectly used in several places to (also) check if a lock is 'live'. Which may cause a false positive effect.

      With this improvement issue those problems need to be solved and replace the current used REPO-1381 'patch' in building the Hippo specific Jackrabbit version, starting with Jackrabbit-2.14.0. 

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                adouma Ate Douma
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: