alodde wrote: > > Does someone can conform my that this is the desired behaviour of xa > transactional jms consumer! I wonder if it is enough to just enable > transaction for the jms consumer as the message exchanges are send > synchronous to the next endpoint and do not care about the nmr. Or does > the messages in the nmr also have to handled transactive (e.g. get > persists) >
The desired behavior of the transactional jms consumer is to rollback if the exchange fails. In your case it doesn't matter weather you choose xa or jms transacted type cause the only transactional resource in your flow is the jms consumer. When you remove transacted="xa" then it works with the default transacted mode which is no transaction. That's why after the failure the message is no longer inside the queue. ----- Ioannis Canellos -- View this message in context: http://old.nabble.com/transaction-servicemix-3.4-tp28532633p28536808.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
