"adrian(a)jboss.org" wrote : For a general XAResource you should do both. | There should be a real (local) timeout in the backend and frontend timeout to cover network splits, etc. Ok, that makes sense. "adrian(a)jboss.org" wrote : My question is why are you using an XAResource for remoting? What state do you have to persist during prepare? Do you really need to vote in 2PC? Remoting has no state, or direct awareness of transactions. However, whatever service you're connecting to by way of Remoting may (and probably does). The reason Remoting 3 has this capability is so that there's a single standard way to propagate transaction state between endpoints - whether it's a database to an app server, two app servers together, or two client applications that don't even know anything about JTA or JCA or anything like that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086022#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...