[jboss-jira] [JBoss JIRA] (WFLY-10427) specify the Hibernate ORM 5.3 JtaPlatform on WildFly for all deployments
Scott Marlow (JIRA)
issues at jboss.org
Tue May 22 14:55:00 EDT 2018
Scott Marlow created WFLY-10427:
-----------------------------------
Summary: specify the Hibernate ORM 5.3 JtaPlatform on WildFly for all deployments
Key: WFLY-10427
URL: https://issues.jboss.org/browse/WFLY-10427
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 13.0.0.CR1
When applications call javax.persistence.Persistence.generateSchema() from active JTA transactions, Hibernate defaults to using org.hibernate.engine.transaction.jta.platform.internal.JBossStandAloneJtaPlatform, which uses com.arjuna.ats.jta.TransactionManager. We cannot use com.arjuna.ats.jta.TransactionManager directly anymore, instead we need to use the WildFly transaction client layer which wraps Arjuna TM.
[https://paste.fedoraproject.org/paste/9y4vn4E0yT77u471LNL-Xw] shows the call stack of where error is thrown by LocalTransaction.verifyAssociation:
{quote}
Caused by: java.lang.IllegalStateException: WFTXN0073: Unexpected provider transaction mismatch; expected TransactionImple < ac, BasicAction: 0:ffff0a0000b0:3831261e:5b045a43:11 status: ActionStatus.RUNNING >, got null[javatest.batch] 13:59:36,576 INFO [stdout] (Thread-130)
at org.wildfly.transaction.client.LocalTransaction.verifyAssociation(LocalTransaction.java:245)
{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list