[infinispan-issues] [JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names
David Lloyd (JIRA)
issues at jboss.org
Tue May 29 10:11:01 EDT 2018
[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583612#comment-13583612 ]
David Lloyd commented on ISPN-9214:
-----------------------------------
I would recommend adding a WildFly strategy (which would be used with WildFly 11 and later) which references {{ContextTransactionManager}} and {{LocalUserTransaction}} instead of the Narayana/Arjuna classes. The existing JBoss strategy would continue to work for JBoss AS 7 and earlier, and WildFly 8, 9, and 10.
The JNDI name has not changed.
> JBossStandaloneJTAManagerLookup is using deprecated integration names
> ---------------------------------------------------------------------
>
> Key: ISPN-9214
> URL: https://issues.jboss.org/browse/ISPN-9214
> Project: Infinispan
> Issue Type: Task
> Components: Core, Integration
> Reporter: Sanne Grinovero
> Assignee: Scott Marlow
> Priority: Minor
>
> Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+, JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}}, needs to instead use the WildFly Transaction Client, or it may see incorrect TX status.
> I assume the Infinispan standalone client will need to be updated as well.
> See:
> - https://hibernate.atlassian.net/browse/HHH-12640
> - https://hibernate.atlassian.net/browse/HHH-12620
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the infinispan-issues
mailing list