CODEWITHSUNDEEP
javarmi
datahaki
datahaki

Reputation: 610

How to obtain the status of an instance of java.rmi.Remote

I have an instance to a class A that implements java.rmi.Remote.

In order to check the health of the connection to the RMI Server, I invoke a custom-made, trivial member function of the instance of A and see if an Exception is thrown. That's not really elegant. Therefore my question:

Is there any native way to check if the connection is available for method invocation on the instance of A, i.e. without the need to actually try to call a member function?

A special case is: Should the RMI server be restarted during the lifetime of the instance of A on the client side, then the instance of A becomes invalid and defunct (although the server might be back up and healthy).

Upvotes: 3

Views: 2630

Answers (2)

user207421
user207421

Reputation: 310850

Your question is founded on a fallacy.

Knowing the status in advance doesn't help you in the slightest. The status test is followed by a timing window which is followed by your use of the server. During the timing window, the status can change. The server could be up when you test and down when you use. Or it could be down when you test and up when you use.

The correct way to determine whether any resource is available is to try to use it. This applies to input files, RMI servers, Web systems, ...

Should the RMI server be restarted during the lifetime of the instance of A on the client side, then the instance of A becomes invalid and defunct (although the server might be back up and healthy).

In this case you will get either a java.rmi.ConnectException or a java.rmi.NoSuchObjectException depending on whether the remote object restarted on a different port or the same port.

Upvotes: 1

Am_I_Helpful
Am_I_Helpful

Reputation: 19158

From Java RMI FAQ :

F.1 At what point is there a "live" connection between the client and the server and how are connections managed?

When a client does a "lookup" operation, a connection is made to the rmiregistry on the specified host. In general, a new connection may or may not be created for a remote call. Connections are cached by the Java RMI transport for future use, so if a connection is free to the right destination for a remote call, then it is used. A client cannot explicitly close a connection to a server, since connections are managed at the Java RMI transport level. Connections will time out if they are unused for a period of time.

Your questions :

  1. Is there any native way to check if the connection is available for method invocation on the instance of A, i.e. without the need to actually try to call a member function?

This question boils down to how to check programmatically that a given server/system is UP. This question has already been answered several times here and several other forums. One such question which answers this is Checking if server is online from Java code.

  1. A special case is: Should the RMI server be restarted during the lifetime of the instance of A on the client side, then the instance of A becomes invalid and defunct (although the server might be back up and healthy).

Then again, the answer is pretty easy. If the instance of the class was busy performing a step within the remote method invocation, then there would be a connection related exception thrown instantly.

Again, from RMI FAQ, D.8 Why can't I get an immediate notification when a client crashes? :

If a TCP connection is held open between the client and the server throughout their interaction, then the server can detect the client reboot(I'm adding here: and vice-versa) when a later attempt to write to the connection fails (including the hourly TCP keepalive packet, if enabled). However, Java RMI is designed not to require such permanent connections forever between client and server(or peers), as it impairs scalability and doesn't help very much.

Given that it is absolutely impossible to instantly determine when a network peer crashes or becomes otherwise unavailable, you must decide how your application should behave when a peer stops responding.

The lookup would keep on working perfectly, till the server is UP and doesn't get down while the client is performing operation on the remote method. You must decide here how your application should behave if the peer restarts. Additionally, there is no such concept as session in RMI.

I hope this answers all of your questions.

Upvotes: 2

Related Questions