Network Faliure Detection Problem

[Rajnish]

Hello All

Network Faliure Detection Problem:
----------------------------------------------------
See figure below:
Client(In JAVA) ----> Router / Switch ----> Router / Switch ---->
Server(In C, C++)

1. Assume all Clients are written in JAVA and server written in C, C+
+.
2. Clients are connected to server on a specific port.
3. All the clients are waiting for their respective response on that
port.
4. Now in case of connection faliure following situations can arrise .
(Assuming that there can be routers and switches in between client
and server connection).
a) Client network cable unplugged or manually disable client
network.
b) Server network cable unplugged or manually disable server
network.
c) Client application may goes down.
d) Server application may goes down.
e) Connection to switch or router breaks or they goes down.

In any case above if the client - Server connection breaks, that
should be notified.

Problem is that if the network goes down for a fraction of second, the
same is not notified.
And the reference which the client holds keep waiting for response.
(As the connection breaks so it will never gets response).


Please suggest for solution if you have faced such problems?


-
Regards
Rajnish Kamboj

[Rajnish]

Hello All

I have not received any solutions to my problem yet.
Any how, the world goes on and on and on.....

As far I have analysed there is no concerete way to do so.
The only way is the Heart Beat Mechanism. The Threshold (beat rate)
rate should not be too high and not too low.

I have achieved the reslts by applying the same. But there is only one
problem.. if the server goes down for a fraction of second then the
same is not detected.

Any suggessions?


-
Regards
Rajnish Kamboj

[Sandeep Kadyan]

yes most peoples follows the Heart Beans mechanism. But the problem you are describing is very common in the client-server model.

For solving this issue, you must have used the time-out mechanism while waiting for response. Same should be done on server. If server is doing some processing which take quite long time, the server can stop the processing by saying that resources are too busy or no sufficient resource are available to process the request etc.

One more comment, like if the switch or route are down for a fraction then the data-communication  protocols like TCP/IP take care for you how to re-send the data (packet) to its destination.

Thank you.
::)
Sandy

--
Sandeep Kadyan
e-M@il:sandeep...@gmail.com
Skype IM: sandeep.kadyan
YIM: theka...@yahoo.com
Cell:-+91 99116 14500

[Rajnish]

Thanks Sandeep

I have applied the same approach which you mentioned of time-out and
polling again.

But of if switch/router are down then will the connection remain
alive .. if TCP/IP protocol sends the packet again. Will the server
make response on the same connection.

If it is not like that then connection between client and server seems
as a virtual entity?


-
Regards
Rajnish Kamboj