How to set the provider transacted?

Question

Hello!
          I got an MDB deployed in a Weblogic 8.1. This MDB Listen for messages from a queue at a MQ 6.0.
          If a mark it as <transaction-type>Bean</transaction-type> then I can deploy it and it consumes messages.
          But if I mark it as <transaction-type>Container</transaction-type> then I get this error message at deploy:
          <2008-apr-06 kl 20:26 CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MyTesting is unable to connect to the JMS destination: MY_QUEUE. The Error was:
          [EJB:010112]The Message Driven Bean 'MyTesting' is transacted, but the provider defined in the EJB is not transacted. Provider should be transacted if onMessage method in MDB is transacted.>
          It seems like it has to do with the "provider", but I can not figure out if the provider is refering to Weblogic or MQ?
          And if either or, how do I configure it to be "transacted"?
          My ejb-jar.xml looks like:
          <message-driven>
          <ejb-name>MyTesting</ejb-name>
          <ejb-class>test.MyTestingMDB</ejb-class>
          <transaction-type>Container</transaction-type>
          <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          <subscription-durability>Durable</subscription-durability>
          </message-driven-destination>
          </message-driven>
          <container-transaction>
          <method>
          <ejb-name>MyTesting</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          My weblogic-ejb-jar.xml looks like:
          <weblogic-enterprise-bean>
          <ejb-name>MyTesting</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>1</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>MY_QUEUE</destination-jndi-name>
          <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
          <provider-url>file:myserver/mq/jndi</provider-url>
          <connection-factory-jndi-name>queue.connection.factory</connection-factory-jndi-name>
          <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
          </message-driven-descriptor>
          <reference-descriptor>
          </reference-descriptor>
          </weblogic-enterprise-bean>
          My jndi-setup looks like:
          def qcf(queue.connection.factory) QMANAGER(queue.manager) TRANSPORT(client) HOSTNAME(127.0.0.1) CHANNEL(MY.CLIENT) PORT(1414) CCSID(819)
          def Q(MY_QUEUE) QUEUE(MY_QUEUE) QMANAGER(queue.manager) TARGCLIENT(JMS) PERSISTENCE(PERS) CCSID(819)
          Any comments is very much appreciated
          Best regards
          Fredrik

Answer 1

Hi Fredrik,
          Yes - just make sure that the CF is XA capable.
          Two notes:
          1 - Note that MQ 6.0 can be incompatible with WL 10.0, as it can supply "JMS 1.1" API support without also supplying JMS 1.0.2 API support. This is a direct violation of the JMS 1.1 specification, but we chose to fix the problem with a patch to our code. If you see a problem here, either (A) contact customer support for a patch or (B) use an older MQ client (perhaps from MQ 5?).
          2 - See also: http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html
          Tom