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

Make LockResource thread safe

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Low
    • Resolution: Fixed
    • None
    • 5.2.0
    • None
    • None

    Description

      The LockResource is an object that can be shared between different threads. Therefor, #close can be invoked concurrently and needs to be synchronized.

      The LockResourceImpl currently returns MutableLock for #getLock. I think it can better return an immutable Lock object instead to avoid potential more concurrency

      Attachments

        Issue Links

          includes

          Bug - A problem which impairs or prevents the functions of the product. CMS-11012 Document the LockResource object is thread safe

          • Low - Low priority, work that comes after other tasks
          • Closed
          is a result of

          Improvement - An improvement or enhancement to an existing feature or task. REPO-1873 Support closing of a LockResource by a different thread

          • 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:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: