Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11243

Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 15.0.0.Final
    • 14.0.0.Final
    • JPA / Hibernate
    • None

    Description

      This addresses what is likely a performance issue in how the TransactionSynchronizationRegistry is looked up for (JPA container managed) persistence contexts used inside of JTA transactions.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16032 (7.2.z) Update WildFlyCustomJtaPlatform#locateTransactionSynchronizationRegistry to use a direct reference to the TransactionSynchronizationRegistry

          • 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
          is related to

          Feature Request - Feature requests from customers and/or users WFLY-11233 Allow EntityManager caching in the JPA container

          • 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

              smarlow1@redhat.com Scott Marlow
              smarlow1@redhat.com Scott Marlow
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: