XA transaction failure
We use a Oracle XA datasource (created using jms-resources) and a XA Queue Connection Factory with a series of MDBs.
We process the JMS message, send it on and update the DB.. This should all be done within one XA transaction.
However, we are finding that the JMS message is being sent on before the db connection is finished.
Is this a known issue in Netweaver CE 7.1? We are using SP7.
Vladimir Pavlov replied
Yep, the first one is managed by the JMS Provider and the second one - by the JMS connector and therefore gets enlisted in global transactions. More information is available [here|http://help.sap.com/saphelp_nwce711/helpdata/EN/46/3155c99f1214dfe10000000a155369/frameset.htm].