Uploaded image for project: 'WildFly Transaction Client'
  1. WildFly Transaction Client
  2. WFTC-72

Remove use of a global lock and lock per transaction

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 1.2.0.Final, 1.1.6.Final
    • None
    • None

    Description

      Using a global lock at some points in the code could cause a bottleneck. Use the transaction as the lock at points that need synchronization instead

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-17265 [GSS](7.2.z) WFTC-72 - Remove use of a global lock and lock per transaction

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              flaviarnn Flavia Rainone
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: