WLS 8.1 an the XAResource interface

Question

Hi I wonder if someone could advise me
          I've created a remote JMS client which is using a third party transaction manager to manage an XA global transaction consisting of many JMS Queue from various WLS servers.
          My problem comes when I try to gain an XAResource from the underlying JMS Queues (needed to enlist them in the overall transaction).
          I take an javax XAQueueSession object which points to a JMS Queue on a WLS 8.1 server and try to invoke the .getXAResource() method to produce the javax XAResource. The problem is it keeps returning me a null pointer.
          the creation of the XAQueueSession is built up in this manner
          1.) Look up connectionFactory from context, cast to an XAQueueConnnectionFactory
          2.) XAQueueConnnectionFactory produces an XAQueueConnection
          3.) XAQueueConnection creates an XAQueueSession
          4.) XAQueueConnection is then started
          5.) XAQueueSession is used to gain an XAResource which produces a null pointer
          Question
          -=-=-=-=-=-=
          1) Does WLS 8.1 support the Javax XAResource interface? if it does is it possible to get an XAResource object from the XAQueueSession?
          Any comments on these quesions would be useful
          Kind Regards
          Barry

Answer 1

Since WLS JMS is clustered, it's a little more complex, because once you start two-phase commit transactions, you need to always go back to the same server in the cluster to resolve them.
          The best-documented way to do this is to use the weblogic.transaction package, which is part of the Javadocs found here:
          http://e-docs.bea.com/wls/docs81/javadocs/index.html
          You need to call the following method from the weblogic.transaction package:
          TxHelper.getClientInterposedTransactionManager()
          This takes a JNDI InitialContext, and also a server name. Once you "prepare" a transaction, you'll have to go back to that server to commit it or roll it back.
          The InterposedTransactionManager object that's returned represents the JTA transaction manager on the server that you named. You can call "getXAResource" on it to get the XAResource that you'll need.
          You will also want to route your JMS calls from your client through the server that you got the transaction manager for. If you don't have a cluster, this is pretty simple. If you have a cluster, then you should create a JMS ConnectionFactory that's targeted to a single server, so that your client calls and your XA calls go to the same node in the cluster.
          The folks on the JTA newsgroup, or BEA Support, should be able to help you with the details if things don't work out, but those are the basics.