Adrian's comment are out of date. We always begin a transaction prior to the receive to support JMS providers where this is required (aka WebSpehreMQ). There was code at one point to be able to toggle this behavior on and off, but it has since been removed in the JCA adapter. anonymous wrote : | We have an XASession that is not enlisted in a global tx. | That's fine the underlying resource will simply not be enlisted. For inbound this is up to the JCA/JMS adapter which is described below. anonymous wrote : | In the case that XASession is created using a ServerSessionPool we want it to fall back to local transaction semantics. For all other cases we want it to have AUTO_ACK semantics. | I am not sure what you are asking. In the case of inbound messages the transaction behavior depends on the transaction attributes of the MDB. For CMT we use XA, for BMT and CMT/NotSupported we use local JMS transactions to support redelivery in the event of a RuntimeException. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041129#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...