[
https://issues.jboss.org/browse/WFLY-10229?page=com.atlassian.jira.plugin...
]
David Lloyd edited comment on WFLY-10229 at 4/13/18 10:02 AM:
--------------------------------------------------------------
I think the question is _why_ the values differed, not _how_ (the how is already
well-understood).
Arjuna is reporting the transaction as "marked rollback" but WFTC is reporting
"rolled back".
was (Author: dmlloyd):
I think the question is _why_ the values differed, not _how_ (the how is already
well-understood).
Arjuna is reporting the transaction as "rolled back" but WFTC is reporting
"marked rollback".
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)