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

Transaction is marked disassociated from application thread when transaction manager reaper thread suspends transaction

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Beta1
    • 11.0.0.Alpha1
    • JPA / Hibernate
    • None
    • Hide

      Using the test fix from https://github.com/wildfly/wildfly/pull/9981, in wildfly/testsuite/integration/basic, run "mvn clean install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase"

      Show
      Using the test fix from https://github.com/wildfly/wildfly/pull/9981 , in wildfly/testsuite/integration/basic, run "mvn clean install -Dtest=org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase"

    Description

      I created a pull request to enable the TxTimeoutTestCase (JBEAP-10550 + WFLY-5319) which required a test change, however, the test is failing for me locally, due to org.wildfly.transaction.client.LocalTransaction.suspend() calling notifyAssociationListeners(false) in the TM reaper "tx timeout" thread, which is wrong, as the app client thread may still be associated with the same transaction.

      https://gist.github.com/scottmarlow/1ae4a4abe98851b3fe6b1e602ba273d7 shows another reaper thread association call being made, that shouldn't be.

      I'm not sure of how the Narayana org.jboss.tm.listener.TransactionListenerRegistry SPI, internally ensured that the reaper thread didn't incorrectly perform association/disassociation but what we have now in WildFly (appears) to be different.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-5319 fix org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase.test_negativeTxTimeoutVerifyReaperThreadCanceledTxTest failure

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10550 Fix TxTimeoutTestCase, ensures that background TM reaper thread doesn't close the transaction scoped entity manager while the application thread is still using it

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFTC-20 Association listeners are not called on commit/rollbackAndDissociate

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: