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

Update jboss-transaction-spi

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Beta1
    • 8.0.0.Alpha4
    • Transactions
    • None

    Description

      The JPA integration test suite tests that the afterCompletion synchonization callback for timed out transactions is called from the TM transaction reaper thread by hard coding the reaper thread name. The latest SPI jar includes an interface method that does the same job. I'd like to update the test suite to use the new SPI method.

      I have marked the jira as a bug since testing against the reaper thread name is brittle.

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBTM-1556 provide way for Synchronization.afterCompletion callee to know if the Reaper thread is calling

          • 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
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: