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

provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.0.0.M5
    • 4.17.3
    • Transaction Core
    • None

    Description

      When the Synchronization.afterCompletion is invoked for EE JPA containers, knowledge of whether the current thread is the Reaper thread (cancelling the transaction from a background thread).

      The fix to this jira will help with handling the JPA 2.1 container concurrency requirements.

      Please implement the solution makes the most sense to you, as this will introduce an additional dependency between other systems and JBossTM/JBossTS that depend on the solution, that will likely be around for a long time.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-331 JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern

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

          Feature Request - Feature requests from customers and/or users JBTM-1699 Changes to the transaction SPI

          • 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.
          • Open
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-2065 Update jboss-transaction-spi

          • 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

              rhn-engineering-mmusgrov Michael Musgrove
              smarlow1@redhat.com Scott Marlow
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: