Hi everyone, I have an oportunity to introduce ServiceMix in my company, through this simple use case:
1. Read a message in a MQSeries queue 2. Call a websevice and pass it the message 3. Get back the message from the ws and post it in an other MQSeries queue But there are some constraints: - This has to be done under the same JMS transaction, so that if there is any problem calling the WS, the get from the first queue is rolled back and the message is not lost. - JMS transaction and NOT XA transaction. - If there is a problem calling the WS the retry has to be delayed (let say 30 sec) to ensure that we are not falling in a "mad" loop of retries. This is very easy with standard Java code I don't know if this is possible with ServiceMix. I know that the jms:consumer has a transacted="jms" attribute but it seems to me that it's a transaction spanning just the get from the queue and the send to the NMR. I have already done the binding of the jms:consumer and the jms:provider with the MQSeries queue, bridged the call to the http:provider through an eip:pipeline (jms:consumer -> eip:pipeline -> http:provider -> jms:provider), but for the JMS transaction and the delayed retry I didn't find anything. Does anyone has any advise? Thank you and best regards Philippe -- View this message in context: http://www.nabble.com/JMS-transaction-and-delayed-retry-tp20130976p20130976.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
