Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-10970

Support closing of a LockResource by a different thread

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: services-4.1.0
    • Fix Version/s: services-4.1.0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      0.5
    • Epic Link:
    • Processed by team:
      Pulsar
    • Sprint:
      Platform 168

      Description

      The LockManager currently only allows closing (unlocking) a previously claimed lock by the same thread.

      A useful/needed improvement is to allow handing the LockResource to a different thread (for example a background scheduler) to close (unlock) the resource after finishing a specific task.

      This will be implemented by simply allowing the LockResource#close() to be invoked by another thread. Then, the LockResource instance itself can be 'shared' as the 'handle' to do this.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: