Should XA really work?

[nl]

Hi all,

I'm trying to configure MS and infinispan for XA transaction support, but I fail.

Env: MS 3.8.0, Infinispan 5.2.10, EAP5

What I get is:

{noformat}
java.lang.NullPointerException
    at org.infinispan.transaction.xa.TransactionXaAdapter.start(TransactionXaAdapter.java:147)
    at org.modeshape.jcr.JcrXaSession.start(JcrXaSession.java:59)
{noformat}

Debugging the code I see that

JcrXaSession.start() is delegating the call to repository.documentStore().xaResource(). DocumentStore is in my case a LocalDocumentStore which in turn delegates to localCache().getAdvancedCache() the which results in a org.infinispan.CacheImpl:

{code}
@Override
   public XAResource getXAResource() {
      return new TransactionXaAdapter(txTable, recoveryManager, txCoordinator, commandsFactory, rpcManager, null, config, name);
   }
{code}

Now this contructor explicitly set the localTransactio to null.

But that one is required in org.inifispan.transaction.xa.TransactionXaAdapter.start():

{code}
@Override
   public void start(Xid externalXid, int i) throws XAException {
      Xid xid = convertXid(externalXid);
      //transform in our internal format in order to be able to serialize
      localTransaction.setXid(xid);
      txTable.addLocalTransactionMapping(localTransaction);
      if (trace) log.tracef("start called on tx %s", this.localTransaction.getGlobalTransaction());
   }
{code}

How should this work in any way?

Thanks for any help,

Niels

[hchiorean]

To my knowledge, XA transactions work as long as Infinispan integrates correctly with a transaction manger.

I have no idea how/if this is supposed to work in EAP 5 though (IIRC we did test this with EAP 6 and Wildfly as part of [MODE-1498] Support JTA transactions - JBoss Issue Tracker).

Also, you need to be aware that even if ISPN integrated correctly with the Tx Manager, Infinispan 5 does not support XA at a cache-store level. So XA will probably work only for the in-memory caches. See this: https://www.mail-archive.com/[e-mail]/msg06426.html and [ISPN-604] Re-design CacheStore transactions - JBoss Issue Tracker for more information about that.