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

Make LockResource thread safe

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2.0
    • Labels:
      None
    • Similar issues:

      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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                aschrijvers Ard Schrijvers
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: