1. Ok, that explains it why you weren't seeing any error on the non-ha jndi restart. 2. Yes, since Naming is used everywhere, more extensive testing would be needed. But since this fix would only add exception catch clause, so normal lookup should work just as is. 3. As for other logic, I was proposing only lookup call since there is current logic for retry already (becuase of server overload, etc.). And I don't see the retry logic in other naming calls (e.g., bind/unbind). In those calls, we'd throw a CommunicationException directly. What do people think? I am tempted to fix only the lookup that should be majority of use cases to minimize the code impact. -Ben View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074328#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...