dotnet remoting: remoting and socket exceptions -- dotnet remoting

Re: remoting and socket exceptions

dr
6/1/2006 8:56:02 AM

I hope thats not the case and if that is the case, then I'd highly recommend
to anyone not to use remoting. Losing your network connection is a real life
scenario that can occur at any time in any situation.

[quoted text, click to view]

Re: remoting and socket exceptions

Mehdi
6/1/2006 5:24:50 PM

[quoted text, click to view]

I'm not really sure of what your problem is. .NET Remoting is generally
used to allow 2 or more applications to communicate across a network. As
you're saying, loss of network connectivity is a common real-life problem
but when that happens it seems prefectly normal to me that remote calls
fail with an exception. Although you've not said it in your original post,
i have the impression that you're using remoting between 2 application on
the same machine. In this case, i believe that a new Shared Memory channel
appeared in .NET 2 that should be a lot more suitable for your situation

Re: remoting and socket exceptions

Spam Catcher
6/1/2006 6:11:28 PM

=?Utf-8?B?ZHI=?= <dr@discussions.microsoft.com> wrote in
news:03BFB081-7978-421C-986B-7CA973FD68A3@microsoft.com:

[quoted text, click to view]

It hasn't been a major issue for us - you just have to handle the error

Re: remoting and socket exceptions

dr
6/2/2006 7:12:01 AM

good points and yes the two apps are running on the same PC. try/catch does
handle it but in the case we are seeing, this exception isn't a one time
thing, it actually seems to occur for a while until the remoting framework
seems to recover. That is why I was wondering if I was doing something
wrong, or if this is a known issue in 1.1. I'm going to rebuild the run with
2.0 and see what happens.

thx.

[quoted text, click to view]

Re: remoting and socket exceptions

dr
6/5/2006 9:34:01 AM

v2.0 of the framework doesn't fix this but switching the channel type to http
and specifyig useIpAddress="false" does fix the problem.

[quoted text, click to view]

Re: remoting and socket exceptions

Mehdi
6/5/2006 7:03:25 PM

[quoted text, click to view]

If you're using .NET 2 and both of your applications are running on the
same box, why don't you use the new IpcChannel? It sounds odd to use an
HttpChannel or even a TcpChannel to do cross-process communication on the

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet remoting group.