[jboss-jira] [JBoss JIRA] (WFLY-8661) Transaction is marked disassociated from application thread when transaction manager reaper thread suspends transaction

[Scott Marlow (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Marlow moved WFTC-19 to WFLY-8661:
----------------------------------------

              Project: WildFly  (was: WildFly Transaction Client)
                  Key: WFLY-8661  (was: WFTC-19)
    Affects Version/s: 11.0.0.Alpha1
                           (was: 1.0.0.Beta21)


> Transaction is marked disassociated from application thread when transaction manager reaper thread suspends transaction
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8661
>                 URL: https://issues.jboss.org/browse/WFLY-8661
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Scott Marlow
>
> 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.  



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)