SONIC MQ - Message Driven Bean with CMT

Question

Hi guys,
I am having hard time with MDB having container managed transaction with TX attribute required. I am using RAD 6.0.1 and the JMS provider is Sonic MQ.I have defined XAConnectionFactory on Sonic side. The MDB runs without any error, but when I shut down the app server the message appears back in the queue. When I use transaction attribute as NOT SUPPORTED everything runs as normal.
Am I missing something on the configuration here?
I am seeing the XA implementation classes in the sonic jar file, but do I need their resource adaptor from sonic?
Thanks
Matt

Answer 1

The current version of the white-paper that Raffi
          refers to covers through 7.0. For 8.1 see also
          http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
          and
          http://edocs.bea.com/wls/docs81/jms/j2ee_components.html
          these features can often make integration easier.
          Tom
          Raffi wrote:
          > Doug,
          >
          > You can find very detailed information on this topic at the link below. All
          > you need to do is specify the destination-jndi-name, initial-context-factory,
          > provider-url, and connection-factory-jndi-name in weblogic-ejb-jar.xml for the
          > non-BEA JMS provider for that specific MDB.
          >
          > ftp://edownload:[email protected]/pub/downloads/jmsproviders.pdf
          >
          > Hope that helps!
          >
          > Raffi
          >
          > Doug Chew <[email protected]> wrote:
          >
          >>Can someone give me an example on how to setup a message driven bean
          >>with a foreign JMS provider using the foreign JMS provider's implementation
          >>of a connection factory. i.e. binding the foreign JMS provider's connection
          >>factory to the JNDI tree.
          >>
          >>Thanks
          >
          >