It's not clear where this exception message is coming from, you mention
calling Console.Print, is that where the exception message is coming from?
Or, does the exception message only occur when debugging and start with "A
first chance exception..." If that's the case, all exceptions that are
thrown produce this message. If the exception is handled it means the
exception didn't cause a problem. For example:
try
{
throw new Exception("Tada");
}
catch (Exception e)
{
return;
}
Will cause A "first chance exception of type 'System.Exception' occurred
in MyApp.exe" message in Visual Studio's output window; but, of course,
there are no ill effects to your application.
With a "No connection could be made because the target machine actively
refused it" exception, it could be that the code "handled" that exception
by simply retrying to get success.
On Wed, 2 May 2007 12:36:57 -0400, Cal Jachs <[EMAIL PROTECTED]>
wrote:
>I am getting very weird behavior. My client calls into a remote object.
That
>remote object then calls back on an object being served by the client (and
>all registered clients who are also serving the same callback object).
>
>When the server's remote object goes to call back on the client's callback
>object (in this case there is just one client), the method call results in
>an exception (see below). Yet despite the exception the call succeeds
behind
>the scenes anyway. I don't understand how that is possible?
>
>Furthermore, weirdly the exception message gets called, and then the
>console.print that comes right after the method call gets executed. I
guess
>this is because the actual exception is being handled on a different
thread.
>
>Either way, this is spooky behavior. yeah it works, but why am I getting
>this message?
>
>The exact exception message is:
>
>"No connection could be made because the target machine actively refused
it"
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
