JMS XASession in Client

Question

          I get the following when trying to use JMS within XA.
          XAResource jmsxa = _XAqueueSession.getXAResource();
          produces error:
          java.lang.IllegalStateException: can only be called from server
          at weblogic.jms.client.JMSXASession.getXAResource(JMSXASession.java:87)
          This code is being run outside of the WLS and I am trying to use JOTM as my transaction
          manager implementation. The documentation refers to needing a different license
          for using XA, is that the case here? Or is it plain old pilot error.
          Thanks,
          don.
          

Answer 1

Don Schafer wrote:
          > Tom,
          >
          > thanks for your responce. Does this mean that for each XA transaction in a remote
          > client I need to use (I am guessing here) RMI?
          For remote WL JMS clients you need to use BEA's TM if
          you want them to participate in a transaction.
          Just start a JTA user transaction and commit it
          when you are done.
          There is nothing special about the way WL JMS is invoked:
          Use a URL to get a WL JNDI context, look up a WL JMS connection
          factory, and go. The fact that RMI is used as the
          communication protocol is immaterial.
          I suggest reading the doc:
          http://edocs.bea.com/wls/docs81/jms/trans.html#1037593
          http://edocs.bea.com/wls/docs81/jta/index.html
          And checking out the sample code that comes
          with WebLogic.
          >
          > Does that mean each enlist call, each commit call wil have additional remote overhead?
          There is no need to manual enlist BEA's JMS with BEA's TM (we do it
          automatically). In fact, it may negatively impact performance
          to do so.
          I think you need not worry about remote overhead.
          >
          > Thanks for your help,
          > don.
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Hi Don,
          >>
          >>No pilot error. The exception text is correct.
          >>WebLogic does not support this call on remote clients.
          >>The same call will work from code called from within a WebLogic
          >>server.
          >>
          >>I suggest filing an enhancement request with customer
          >>support, and letting your BEA sales rep know about your need.
          >>
          >>The alternative is to use BEA as the transaction monitor.
          >>
          >>Tom, BEA
          >>
          >>P.S. With the current product, JMS capability implies
          >>that there must already be a XA capability. It is not
          >>possible to purchase JMS capability without getting XA.
          >>
          >>Don Schaefer wrote:
          >>
          >>>I get the following when trying to use JMS within XA.
          >>>
          >>>XAResource jmsxa = _XAqueueSession.getXAResource();
          >>>
          >>>produces error:
          >>>
          >>>java.lang.IllegalStateException: can only be called from server
          >>> at weblogic.jms.client.JMSXASession.getXAResource(JMSXASession.java:87)
          >>>..
          >>>
          >>>This code is being run outside of the WLS and I am trying to use JOTM
          >>
          >>as my transaction
          >>
          >>>manager implementation. The documentation refers to needing a different
          >>
          >>license
          >>
          >>>for using XA, is that the case here? Or is it plain old pilot error.
          >>>
          >>>Thanks,
          >>>don.
          >>>
          >>>
          >>>
          >>>
          >>>
          >>
          >