The spec seems to be completely silent on this. I would be interested to know how JCA treats this. Does the JCA layer ever close connections that have XASessions that are still enlisted in a global tx, or does it never do this. Problem, is, even if the JCA layer never does this, Jo dumb user who is using the XAConnection might, and we need to know what to do when he closes that connection that has sessions still enlisted. For now, I will treat explicitly closing a connection after prepare has been called but before commit/rollback has been called the same as a server crash, i.e. the resource manager retains the prepared state so it's available to any subsequent recover() calls. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995560#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...