I have tried Clebert's suggestion mentioned in the other post of changing the server id in messaging-server.xml: | <constructor> | <!-- ServerPeerID --> | <arg type="java.lang.String" value="server.0" /> | <!-- DefaultQueueJNDIContext --> | <arg type="java.lang.String" value="/queue" /> | <!-- DefaultTopicJNDIContext --> | <arg type="java.lang.String" value="/topic" /> | </constructor> | This seems to make things work if you don't try and close the failed session and connection. If you uncomment the code to try and close the session and connection, then the sending of messages to the second server doesn't work at all, with the same "Object with oid was not found in the Dispatcher" error mentioned previously. On the server, the following entry is logged: 2006-11-09 16:45:20,457 WARN [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] A problem has been detected with the connection to remote client 4h39k9-33iqxv-euaqkont-1-euaqkq0f-9. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984400#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...