Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-1381

Concurrent session access in Jackrabbit's LockManager timeout handler

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: 2.26.17, 3.0.1, 3.1.0
    • Fix Version/s: 3.2.0
    • Component/s: None
    • Labels:

      Description

      We often see issues due to session write concurrency when unlocking and refreshing locks. Jackrabbit pro-actively times out locks on a dedicated thread. When timeout and unlocks or refreshes of locks happen simultaneously you see failures due to concurrent session access. Since we now have our own just-in-time unlocking logic in place, these pro-active unlocks seem not to be necessary any more. We can disable it in our patched Jackrabbit.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              uhommes Unico Hommes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: