What you're saying is that if you put the message back on the queue (nack it) on rollback then you can't guarantee ordering, since the session could do work in different transactions that could rollback in a different order. However if you're not using XA then it seems to me that order can be maintained, even if you have competing consumers on the same queue, since on rollback you don't need to NACK the message back to the queue (where it could get picked up by a competing consumer), instead you can just recover it locally in the session, i.e. just resubmit it to the onMessage method, in the same way you do with session.recover. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958145#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...