CMT and using non-Weblogic JMS in a session bean

Question

          I am writing a session bean which sends a JMS message using a non-weblogic JMS
          provider. This bean is marked for CMT and I want the JMS send to participate in
          this CMT as well. My understanding is that I should be able to do this by defining
          a <resource-ref> element in the ejb-jar.xml and a corresponding <resource-descriptor>
          element in the weblogic-ejb-jar.xml file. The bean would then use the <res-ref-name>
          defined under the <resource-ref> element to lookup the connection factory. What
          do I have to put in weblogic-ejb-jar.xml file to make sure that the connection
          factory specified in <res-ref-name> maps to a connection factory that is in a
          foreign JNDI provider (e.g. in the non-Weblogic JMS provider's JNDI) and not in
          Weblogic's JNDI?
          Thanks in advance for your help.
          

Answer 1

It sounds like you're using Tibco JMS to receive messages from the MDB, and
          then to send out a message. WLS 7.0 will handle the transaction enlistment
          properly when it receives messages for the MDB, but you'll have to enlist
          the JMS provider yourself when you send the message, using the white paper
          that Tom pointed you to as a guide.
          In WLS 8.1, coming soon, we'll automatically enlist the provider in the
          transaction if you look it up using a "resource-ref" element in the EJB like
          you described. Today, you can use that element but no transaction
          enlistement is being done.
          greg
          "Venkat" <[email protected]> wrote in message
          news:[email protected]...
          >
          > We also need this feature.
          > We are using Weblogic 7.0 and Tibco JMS 3.0,
          > which supports XA.
          >
          > We are mainly interested in subscribing using MDB
          > and publishing using a session bean in one transaction.
          > Do you think by using resource-refs in conjunction
          > with registering with Weblogic JNDI during startup
          > can do the job?
          >
          > Or how about using XAConnectionFactory and XASession
          > classes for JMS publishing ?
          >
          > Thanks.
          >
          > Tom Barnes <[email protected]> wrote:
          > >Hi Mihir,
          > >
          > >Support for automatic enlistment of foreign JMS vendors
          > >via the resource-ref approach is not available in WLS.
          > >This support will be available in the next release:
          > >limited access beta is available now, public beta is available
          > >in 2-3 months. You are the first customer I've heard of that
          > >asked for this feature. Very cool. Good timing.
          > >
          > >As you are not using WebLogic JMS, you will need to do the
          > >transaction enlistment yourself. This isn't that hard
          > >to do. I suggest that you refer to the integrating foreign
          > >JMS vendor white-paper available on dev2dev.bea.com.
          > >Also, refer to the integrating transactions with
          > >MQSeries integration paper, which will likely serve your
          > >purposes better. Note that some JMS vendors
          > >have problems with concurrent transactions in a single
          > >JMS connection, or with transactions that attempt
          > >to switch threads (eg. suspend() in one thread
          > >and resume() in another).
          > >
          >
          >http://dev2dev.bea.com/resourcelibrary/whitepapersdetail.jsp?highlight=whit
          epapers&filePath=components%2Fdev2dev%2Fresourcelibrary%2Fwhitepapers%2Fwp_j
          msproviders.htm
          >
          >http://dev2dev.bea.com/resourcelibrary/whitepapersdetail.jsp?highlight=whit
          epapers&filePath=components%2Fdev2dev%2Fresourcelibrary%2Fwhitepapers%2Fwp_j
          tatransactions.htm
          > >
          > >Tom
          > >
          > >mihir sharma wrote:
          > >> I am writing a session bean which sends a JMS message using a
          non-weblogic
          > >JMS
          > >> provider. This bean is marked for CMT and I want the JMS send to
          participate
          > >in
          > >> this CMT as well. My understanding is that I should be able to do this
          > >by defining
          > >> a <resource-ref> element in the ejb-jar.xml and a corresponding
          <resource-descriptor>
          > >> element in the weblogic-ejb-jar.xml file. The bean would then use the
          > ><res-ref-name>
          > >> defined under the <resource-ref> element to lookup the connection
          factory.
          > >What
          > >> do I have to put in weblogic-ejb-jar.xml file to make sure that the
          > >connection
          > >> factory specified in <res-ref-name> maps to a connection factory that
          > >is in a
          > >> foreign JNDI provider (e.g. in the non-Weblogic JMS provider's JNDI)
          > >and not in
          > >> Weblogic's JNDI?
          > >>
          > >> Thanks in advance for your help.
          > >>
          > >
          >