Mehdi > There is no way to find a work around? > Here are somethings that I can think of from the top of my head..
1. For each received message, acknowledge just one message at a time, which we know is ready to be acked (By default ack on a message acks all messages read during that Session) - This is the simplest way to do this and is available for example with the Sun JMS implementation <http://docs.sun.com/source/819-0068/progfeatures.html#wp33087> 2. Use a ServerSessionPool (defined on the JMX spec but listed as "optional") to create multiple sessions so that the receipt of every single message could take place over a new Session. Your JMS drivers/provider should support this.. 3. Implement a manual Session pooling, where multiple Sessions are used to process messages concurrently - so that each Session/Message could be acked independently via a separate Session 4. Integrate with Atomikos (http://www.atomikos.com/products.html#ate) However, some options may require the support of your JMS provider, while the more generic option to support JTA transactions from Synapse, would require some coding :).. Since we already have a JIRA in Synapse, we will work on this in the relative order of priority, however if this critical for your deployment and you need this urgently, drop me a mail at: [EMAIL PROTECTED] to see what might be possible asankha
