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

[Backport 12.1] LockManager usage issue in clustered environment

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.1
    • Labels:
      None
    • Similar issues:
    • Processed by team:
      Turing
    • Sprint:
      Turing Sprint 173

      Description

      Since the lock via the LockManager does not involve any jcr locking, it does never trigger a cluster sync. This means that when we have a lock, then if after the lock we have code that results in jcr nodes being persisted, then in general after obtaining the lock, always a cluster wide sync has to be triggered via session.refresh

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                aschrijvers Ard Schrijvers
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: