Ovidiu wrote : To spell this out for you, so you won't go over is again: The current code, that is in the SVN, does not behave this way. This is understandable, it's just a prototype. I was going over the use cases for which we need test cases, so we can make sure the correct behavior is preserved in the future. The correct behavior is "transparently copying the transactional state (the corresponding TxState instance) into the new ResourceManager and send the messages over the new connection when transaction commits." Please note the use of the word "transparent". | The Transaction still has any pending transaction on its buffer when a connection is failed over. The code it's not a prototype IMO, it's one of the layers of the failover and currently I'm not considering the first layer yet. I have started from the second layer as when we started we were not sure what was going to happen with Remoting. I want to finish this layer now before starting on the first layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981021#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...