HARMIClient catches a number of java.rmi exception types that indicate a request did not reach the server. It then attempts to failover, and keeps catching exceptions until all targets are exhausted. If all targets are exhausted, the last exception caught is wrapped in a RemoteException and thrown.
This issue is to specially cache any java.rmi.NoSuchObjectException. If all targets are exhausted and an NSOE was caught, we wrap that instead of the last exception caught.
Intent here is the NSOE provides information that a target server is listening on the given port but that the client-side naming stub is out of sync with the server-side RMI runtime. This is potentially useful to the caller; e.g. see the parent issue.