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

Leverage LockManager for the RepositoryScheduler replacing the deprecated HippoLock usage

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • 5.1.0
    • 5.1.0
    • None
    • None

    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

          is backported by

          New Feature - A new feature of the product, which has yet to be developed. REPO-1879 [Backport 12.0] Implement new LockManager service and replace all deprecated HippoLock and HippoLockManager usages

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: