Stopping destinations and getting clients to reconnect is an unsupported feature in JBossMQ. There is no mechanism to push the error to the client. One way to solve the problem (though it isn't very good) would be to close all connections that have active receivers (subscribers not receivers in BasicQueue) on the destination. This would cause the ExceptionListener to fire due to the lost connection. But this isn't implemented. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106508#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...