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

[Backport 11.2] LockManager usage issue in clustered environment

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 4.2.6
    • None
    • None
    • 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

          clones

          Bug - A problem which impairs or prevents the functions of the product. REPO-1917 [Backport 12.0] LockManager usage issue in clustered environment

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed
          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. REPO-1919 [Backport 10.2] LockManager usage issue in clustered environment

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. REPO-1915 LockManager usage issue in clustered environment

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: