Remoting timeout not working

[=?Utf-8?B?S29zbW8=?=]

Hi,

When the remoting server is not available (it is unreachanble/ closed/
non-existent), making a call on the remoted object takes 45 seconds, and
this timeout value cannot be changed.

MSDN says this problem is fixed by setting the channel timeout property, but
this doesn't work.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=892614&SiteID=1

There are workarounds, like launching the remoting request on a new thread,
but this is only a workaround. I would like to know if there is a 'real'
solution to this from Microsoft, like a working timout setting?

Thanks,
Kosmo

[=?Utf-8?B?UGV0ZXIgUml0Y2hpZSBbQyMgTVZQXQ==?=]

RE: Remoting timeout not working

The timeout you're asking about is the timeout of .NET remoting
communications between the server and the client. If the server is not
responding that's a timeout of DNS/TCP, which is before .NET remoting really
gets involved.

The link you provide details that someone is abstracting a ping to the
server to keep track of liveliness of that server separately, which is
basically what you'll have to do.

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.

http://www.peterRitchie.com/blog/

Microsoft MVP, Visual Developer - Visual C#


"Kosmo" wrote:

Hi,
>
When the remoting server is not available (it is unreachanble/ closed/
non-existent), making a call on the remoted object takes 45 seconds, and
this timeout value cannot be changed.
>
MSDN says this problem is fixed by setting the channel timeout property, but
this doesn't work.
>

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=892614&SiteID=1

>
There are workarounds, like launching the remoting request on a new thread,
but this is only a workaround. I would like to know if there is a 'real'
solution to this from Microsoft, like a working timout setting?
>
Thanks,
Kosmo