[
https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin...
]
Scott Marlow commented on WFLY-10229:
-------------------------------------
[~tomjenkinson]
{quote}
I don't understand why ContextTransactionManager is reporting it is rolled back if
Narayana thinks it is only marked rollback - but perhaps that was explained on the private
thread?
{quote}
I don't have a full understanding of why ContextTransactionManager is reporting
different values from TransactionManager.getStatus() than the Narayna
TransactionSynchronizationRegistry.getStatus() but I suspect it is related to
ContextTransactionManager maintaining its own transaction status code.
org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus()
should use org.wildfly.transaction.client.ContextTransactionManager.getStatus()
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-10229
URL:
https://issues.jboss.org/browse/WFLY-10229
Project: WildFly
Issue Type: Task
Components: Transactions
Reporter: Scott Marlow
Assignee: David Lloyd
Fix For: 13.0.0.Beta1
org.jboss.as.txn.service.internal.tsr.TransactionSynchronizationRegistryWrapper.getStatus()
is currently using com.arjuna.ats.jta.TransactionManager, instead it should use
org.wildfly.transaction.client.ContextTransactionManager.getStatus().
I'm seeing a case in Hibernate ORM 5.3, where
org.wildfly.transaction.client.ContextTransactionManager.getStatus() returns 4 but
TransactionSynchronizationRegistryWrapper.getStatus() returns 1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)