If a client-side RMI runtime attempts a JRMP connection to a server's TCP port that does not process JRMP (at least not correctly) in such a way that no data is returned in response to the initial handshake, and the connection isn't closed either, then the client will hang indefinitely. (This could happen if the original RMI server has gone down, and a new non-RMI server has started listening on the same port.)

It would be nice if the JRMP client would set a (perhaps configurable) timeout for response to the initial JRMP handshake for situations like this, so that the connection attempt would eventually fail.