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

Leverage LockManager for the RepositoryScheduler replacing the deprecated HippoLock usage

    XMLWordPrintable

    Details

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

      Description

      CMS-10970 will add support for delegating closing a LockResource to a different thread, which allows then also using the LockManager for the RepositoryScheduler (specifically: the JcrJobStore).

      The jobs to be executed are created, executed and released through Quartz background threads. Which all may be different threads (per job), so locking and releasing of such jobs requires the above capability.

      The LockResource object will be passed onto Quartz, and retrieved again, via the Quartz OperableTrigger#jobDataMap object.

        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: