Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-610

Restore mutex handling on LockManager

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 4.8.0, 4.9.0
    • None
    • Transaction Core
    • None

    Description

      It looks like someone tried to optimize the synchronizations around LockManager, probably for HP-MS performance tuning. Unfortunately they didn't fully understand the implications. Backing out to original approach until/unless performance becomes an issue again.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. JBTM-618 Reduce synchronization boundaries on LockManager.setlock

          • 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.
          • Closed

          Activity

            People

              nmcl2001 Mark Little
              nmcl2001 Mark Little
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: