Any idea? I get the feeling that the real problem is an incompatibility between asynchronicity and the propagation of the transaction context but it is an impossibility or something i'm unfamiliar with? And is this incompatibility specific to JMS or more general? After all the transaction context is propagated to a different thread (from the client thread to the server thread) by rmi during a remote transactional invocation, so it doesn't have to be strictly thread-local. On the other hand even in the EJB 3.1 spec, it is mentioned that for the new @Asynchronous methods, the transaction context will not be propagated from the caller to the callee. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254653#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...