[Mono-devel-list] Tracing execution path?

Ben Maurer bmaurer at ximian.com
Mon Dec 13 08:36:11 EST 2004

> Hi,
> I'm trying to trace the execution path (in managed code) for a web
> service request. I tried using the --trace option, however when I do
> this, I receive the following exception in my client
> "System.Net.WebException: The underlying connection was closed: Unable
> to connect to the remote server."
> Redirecting output to a file did not help either.
> My Web service is running on mono and the client is running on MS.Net.
> If I use for example "--trace=N:System.Net" instead of "--trace" I no
> longer see this exception and the client's web service request succeeds.
> Any idea why I am seeing this exception in my client and how I can fix
> it so that I can see the entire managed execution path?

My best guess here is that something is getting a timeout; tracing can
take a very, very long time.

If you can make a filter for what you want that would be best (as it will
be hard to find anything in the huge --trace anyways). Either that or
increase the timeout (it is probably in web.config).

-- Ben

More information about the Mono-devel-list mailing list