XA Transactions with SOASuite JMS Adapter by Martien van den Akker
January 25, 2017 1 Comment
JMS is perfect for setting transaction boundaries and in OSB it is pretty clear on how JMS transactions are handled. However, in SOASuite using the JMS adapter the SOA Infrastructure is handling your JMS transactions by default; and messages are removed from the queue rightaway because the Get’s are Auto-acknowledged. If something fails, you would expect that messages are rolled back to the JMS queue and eventually moved to the error queue. But, again by default, not with the SOASuite/JMS Adapter. In that case the BPEL process, for instance, fails and get’s in a recovery state, to be handled in the ‘Error Hospital’in Enterprise Manager. But I want JMS to handle it! (Says the little boy…)
So how do we accomplish that? Today I got the chance to figure that out.
Start with a JMS setup with a JMS Server, Module and a Queue with an Error Queue that is configured to be the error destination on the first queue. On the first queue set a redelivery limit to 3 and a redelivery delay on for instance 60000 ms (or something like that). I’m not going in to that here.
Create also a Connection Factory in the JMS Module with a proper jndi, something like ‘jms/myApplicationCF’.
In the JMS adapter on SOASuite there are several OutboundConnectionFactories already pre-configured. It is quite convenient to use the one with JNDI ‘eis/wls/Queue’. But if you look into that, you’ll see that it uses the default WebLogic JMS Connection factory ‘weblogic.jms.XAConnectionFactory’. Not much wrong with that, but you can’t configure that for your own particular situation. But more over it is configured with ‘AcknowledgeMode’ = ‘AUTO_ACKNOWLEDGE’. As you can read in the docs there are three values for the AcknowledgeMode:
DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messagesAUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a messageCLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message’s acknowledge method
So create a new outbound connection factory, with a JNDI like ‘eis/jms/MyApp’.
Now, apparently we don’t want ‘AUTO_ACKNOWLEDGE’, because that would cause the message-get acknowledged ‘On Get’. So you could rollback until ‘Saint Juttemis’ (as we say in our family) but it won’t go back on the queue. Dups aren’t ok with me, so I’ll choose ‘CLIENT_ACKNOWLEDGE’ here. Then there’s another option: ‘IsTransacted’. I want that one on ‘true’. Then in ConnectionFactoryLocation, you’d put the JNDI of your JMS Connection factory, in my example ‘jms/myApplicationCF’. So you’ll get something like: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
![image[7][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/image7222.png?w=20&h=20 "image[7][2][2][2]"){kind=small}
![clip_image002[8][4][2][2][2]](https://soacommunity.files.wordpress.com/2013/04/clip_image00284222.jpg?w=26&h=23 "clip_image002[8][4][2][2][2]"){kind=small}
In our case we had two roles: shippers and suppliers. There are a few differences between the two tradingpartner roles, but all the shippers have the same capabilities as well as all the suppliers. 
PaaS Community Blog 