JIRA for this is http://jira.jboss.com/jira/browse/JBAS-4615 . This is basically implemented and tested in branch JBoss_4_0_5_GA_JBAS-4574; needs to be ported to the regular branches. Just a note for the record: the fix we're implementing is based on catching java.rmi.NoSuchObjectException. If the naming service uses Remoting or even the pooled or http invokers, that exception won't be thrown. However, usually if those invokers are used the client-side proxy will still be valid after a restart (unless the server address or port has changed.) Fixing the edge case where the address or port has changed would involve catching and retrying after a large variety of exceptions, which is too big a behavior change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075629#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...