Check if server is alive in drb

Hi,

Is there any elegant method for checking if a drb server is still
alive from the client side?

My server notifies my client when it finished a job through the
observer method. However, it is possible that the server dies (or the
network connection gets broken), and I need to detect this. I
implemented a thread which continously “pings” (calls a simple
remote_obj.ping) and rescues any exceptions in this method call. Is
there a better solution out there?

Thanks,
Tiberiu

On Aug 28, 2007, at 01:15, Mr_Tibs wrote:

Is there any elegant method for checking if a drb server is still
alive from the client side?

My server notifies my client when it finished a job through the
observer method. However, it is possible that the server dies (or the
network connection gets broken), and I need to detect this. I
implemented a thread which continously “pings” (calls a simple
remote_obj.ping) and rescues any exceptions in this method call. Is
there a better solution out there?

Nope.

On Aug 28, 2007, at 2:15 AM, Mr_Tibs wrote:

My server notifies my client when it finished a job through the
observer method. However, it is possible that the server dies (or the
network connection gets broken), and I need to detect this. I
implemented a thread which continously “pings” (calls a simple
remote_obj.ping) and rescues any exceptions in this method call. Is
there a better solution out there?

depending on how many clients there are each one can call a method on
the server that never returns (Thread.sleep). if the method ever
returns in the client it knows the server has died. this obviously
only works for a small number of clients.

a @ http://drawohara.com/

ara.t.howard wrote:

hmm that’s good idea for keeping connections alive i guess :slight_smile: i had
problems that frequent requests over ssl were making huge overhead.