Re: Interesting Socket error when contacting .net remote server
- From: "Goran Sliskovic" <gsliskov@xxxxxxxxx>
- Date: Fri, 29 Sep 2006 16:23:30 +0200
"balak" <balak@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0B68990E-120C-4BE7-A462-555E66C48D8B@xxxxxxxxxxxxxxxx
Server machineexceptions
===========
I have a .net remote server application (console app hosting a .net remote
object) installed on the server machine.
Client machine
==========
I also have a windows service on another machine (client) that creates the
remote object and makes calls on it. The remote object is invoked as a
singleton object.
Now the server machine gets rebooted often (by design) and so the windows
service on the client machine has retry logic (by catching socket
and sleeping for a few minutes and retrying).get
What is happening is that after reboot of the server machine , when the
windows service on client again creates and calls on the remote object, I
socket errors (host unreachable) even though the server app has startedand
ready to serve objects.indicating
Any idea why this might be happening?
Is there any information that is cached by the remoting framework
that the server is unavailable (while the server was rebooting and theremote
call failed) and that is preventing future calls?
Hi,
I are you connecting through router or is the server on LAN?
Regards,
Goran
.
- Follow-Ups:
- Prev by Date: Type.InvokeMethod not working in remote server object.
- Next by Date: Re: Interesting Socket error when contacting .net remote server
- Previous by thread: Type.InvokeMethod not working in remote server object.
- Next by thread: Re: Interesting Socket error when contacting .net remote server
- Index(es):
Relevant Pages
|
Loading