JMSBridgesXA/xa-compliant-oracleaq - how do TX work? StartupClass questions

Question

Hallo all,
          yesterday we called in our (very simple) MDB sessionContext.setRollbackOnly().
          Expected behavior: Oracle AQ should resend the JMS message after a while (queue_table still needs to have the message).
          Seen behavior: The JMS message was removed from Oracle AQ queue table and has not been resent. It got lost completely.
          Question: What do we have to do, that the MDB supports JMS transactions? We already defined Required in the deployment descriptor and referenced "AQXAJMSConnectionFactory" as factory in weblogic-ejb.jar.xml.
          Is there the requirement to use resource-ref's (probably this is not the case for incoming MDB's. Only interesting if doing a JMS send inside a MDB or Stateless Session EJB?).
          How does the JMSBrdigesXA project work together with BEA JTA TransactionManager?
          DipsStartupClass: What does it do exactly?
          It seems to instantiate the required AQ Factory and Queue classes and binds them to BEA JNDI.
          But also it creates a AQjmsConnection, AQjmsSession and Destination and starts the Connection and Session! (e.g createXAQueueConnection).
          Why does it have to do this?
          MDB's deployed to BEA JMS and referencing a JMSConnectionFactory don't need a StartupClass, so the normal factories seem to establish the connection internally (is BEA pooling JMS resources here internally in addition???)
          Does it make any difference using in Constants "thin" or "oci8"?
          The class DipsAQXAQueueConnection and method createXAQueueSession() creates an OracleXAConnection by passing getOCIConnectionPool().getConnection().
          What does this mean? Why OCI? Is the "thin" property working nevertheless?
          Does the DipsStartupClass create ONE Oracle connection to Oracle AQ or do we have to specify somewhere any Oracle pool size?
          What would we have to do if multiple MDB's have to listen to different queues?
          Looks like that we need multiple StartupClasses because of queue_table_name and queue bindings (JNDI AQJMSQueue).
          But what does this mean to the AQXAJMSConnectionFactory?
          Would we have to bind it multiple times under different names (e.g 3 MDB's, 3 factories)?
          How many Oracle AQ DB connections have to be open?
          Is there a new DipsAQXAConnectionFactory / DipsAQConnectionFactory which does all the things internally on the fly so we can deploy MDB's as we would work with BEA JMS (besides StartupClass for the "Referencable" solution)?
          What did you change for your tests the oracle.jms.DipsAQXAQueueSession constructor to? The current sources of JMSBridgesXA Oracle AQ look incompatible with aqapi13.jar (I tried also aqapi.jar and aqapi11.jar)!
          AQjmsSession needs a fith argument java.sql.Connection.
          Shall we call:
          super(aqjc, sessAck, flag, j, oraXAConn.getConnection())
          or
          super(aqjc, sessAck, flag, j, null)
          May be the first (we did that) be the reason of the NON TX behavior if java.sql.Connection is set to AutoCommit by default to true?
          Somewhere in this weblogic.developer.interest.jms forum I read that only Oracle 10g aqapi.jar is XA cabable?
          We have to use Oracle 9.2.0.6 and I defenitly have to use TX's.
          I even would have to get this working:
          1. MDB recieves AQ JMS message
          2. does some business logic
          3. send a JMS message to another queue
          4. commits if 2 and 3 was successful by removing the JMS message from the Oracle AQ.
          However, a MDB rollback MUST ensure, that the received Oracle AQ/JMS message won't be lost.
          With best regards
          Thomas Heiss
          Message was edited by:
          Thomas.Heiss
          Message was edited by:
          Thomas.Heiss

Answer 1

Dear Eric,
          Thank you very much for your input.
          Unfortunately also a RuntimeException does not rollback/keep the message in AQ queue in our test MDB environment.
          So TX is still some open issue for us.
          Today we made the decision to go with a MapMessage (instead of Oracle custom data type) and do all AQ receive/send stuff manually (because of time running away).
          Meanwhile I also tried Oracle 10g R2 database aqapi13.jar; has a completely different constructor in AQjmsSession which does not seem to be compatible anymore with DipsStartupClass package.
          I wonder how aqapi13.jar from Oracle 10g should work without DipsStartupClass.
          Oracle 10g application server may provide an adapter solution; but I would need to find, check and test it with BEA MDB's first.
          Today we found out, that AQ propagation needs queues defined to be multi_consumer queues.
          Unfortunately settings multi_consumer TRUE and a DEQUEUE (in aqapi13.jar with DipsStartupClass) does not play well together. It's missing a consumer name.
          Then it will only work with recipient list.
          I hope next weeks I will find some Oracle AQ guru which may show me a way out of all this disaster :)
          Regards
          Thomas Heiss