How to log more info on System.Web.HttpException: Request timed ou

[Mattias Blomqvist]

Some of our users are complaining about long response time on some of our
pages.
Problem is that we can not reproduce the long response time.

Our error log has also logged: System.Web.HttpException: Request timed out
(Sadly without any stacktrace or other useful information).

Is it possible to log stacktrace for this type of error or in other way
finding out where in our code or what underlying service that is taking so
long?

We are using:
* .Net 3.5
* Microsoft.Practices.EnterpriseLibrary
* Windows Server 2008 64bit

/Regards Mattias

 

[Bob Barrows]

Some of our users are complaining about long response time on some of
our pages.
Problem is that we can not reproduce the long response time.

Our error log has also logged: System.Web.HttpException: Request
timed out (Sadly without any stacktrace or other useful information).

Is it possible to log stacktrace for this type of error or in other
way finding out where in our code or what underlying service that is
taking so long?

I think you can turn tracing on in web.config - search online help or
the web. And ...

**********canned wrong newsgroup reply****************************
There was no way for you to know it (except maybe by browsing through
some of the previous questions before posting yours - always a
recommended practice), but this is a classic (COM-based) asp newsgroup.
ASP.Net is a different technology from classic ASP. While you may be
lucky enough to find a dotnet-savvy person here who can answer your
question, you can eliminate the luck factor by posting your question to
a newsgroup where the dotnet-savvy people hang out. I suggest

microsoft.public.dotnet.framework.aspnet.

There are also forums at www.asp.net where you can find a lot of people
to help you.
**********canned wrong newsgroup reply****************************

 

[Evertjan.]

Bob Barrows wrote on 11 mrt 2010 in
microsoft.public.inetserver.asp.general:

I think you can turn tracing on in web.config - search online help or
the web. And ...

**********canned wrong newsgroup reply****************************
There was no way for you to know it (except maybe by browsing through
some of the previous questions before posting yours - always a
recommended practice), but this is a classic (COM-based) asp newsgroup.
ASP.Net is a different technology from classic ASP. While you may be
lucky enough to find a dotnet-savvy person here who can answer your
question, you can eliminate the luck factor by posting your question to
a newsgroup where the dotnet-savvy people hang out. I suggest

microsoft.public.dotnet.framework.aspnet.

There are also forums at www.asp.net where you can find a lot of people
to help you.
**********canned wrong newsgroup reply****************************

Anyway the BobBarrows-response-time was pretty short.

 

[Bob Barrows]

Bob Barrows wrote on 11 mrt 2010 in

Anyway the BobBarrows-response-time was pretty short.

Can't always count on that though ... ;-)

 

[Mattias Blomqvist]

We can't use Tracing as it would affect the performance to much.

I have now made a customCallHandler instead (implementing ICallHandler) with
the hope it will find our problem and just log that method when elapsed time
in a method is over X.

We will see after the next release

Thanks for the response.

 

[Evertjan.]

=?Utf-8?B?TWF0dGlhcyBCbG9tcXZpc3Q=?= wrote on 16 mrt 2010 in
microsoft.public.inetserver.asp.general:

We can't use Tracing as it would affect the performance to much.

I have now made a customCallHandler instead (implementing
ICallHandler) with the hope it will find our problem and just log that
method when elapsed time in a method is over X.

We will see after the next release

Thanks for the response.

What response?

[please always quote on usenet]