[ https://issues.jboss.org/browse/WFLY-8661?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8661: ------------------------------------ [~dmlloyd] I tried the "counter" change last night but noticed that the notifyAssociationListeners() call only is happening from the TM reaper (timeout) thread but not the application thread. For the TM Reaper thread, we seem to reach the path of handling "whileSuspended/whileResumed" in org.wildfly.transaction.client.AbstractTransaction.performConsumer(ExceptionObjIntConsumer<T, E> consumer, T param1, int param2) but don't seem to reach that method at all in the application thread once the TM Reaper thread reaches AbstractTransaction.performConsumer. I expect that the application thread will disassociate itself from the transaction, at which time I will decrement the jpa container counter but the association listener is not getting called back it seems after the TM reaper thread cancels the transaction. Also, when the JPA container calls transaction.registerAssociationListener(), should I start the counter at one, or should I expect the association listener to be called immediately, to reflect the current active transaction that is already associated with the application thread? For now, I am starting the counter at one but we should agree on what should happen, so that the jpa counter starts at the correct value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)