"ovidiu.feodorov(a)jboss.com" wrote : | | If there is no distributed transaction, then there can be no "prepare and commit work on the transaction", hence the session is non-transactional. That is one solution, but it isn't a logical necessity. Other conforming implementations would be that messages (or acks) are stored up in the session, until work is started in a transaction, then the previous work done is transferred into the transaction. In fact, a similar conversion already happens in certain situations: See ResourceManager::convertTx(LocalTx anonXid, Xid xid) throws XAException Which converts work done outside a global tx into work done inside the global tx. As I said earlier in this thread, this is a religious argument and I don't think we'll find any conclusion in the JMS spec, since it is sparse at the best of times, especially the XA stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968774#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...