Geek Answers Handbook

How to find a dead end on ASP.Net

I am using .Net 2.0 and my site seems to have reached a certain blocking state in a certain period. It stops working until I rework the application pool or change anything in the web.config file. I think the dead end is causing this problem.

I am wondering if there is any tool for debugging / checking the site to find code that could cause a deadlock.

Right now I had to set the processing interval to 10 minutes, which is very bad, but this is the only way to solve the problem, and there are a lot of codes on the site, and I need to find the problem. If I use a DOS attack tool, can I find the page / code block that causes this problem? If I can, which tool is better to check?

Hooray!

EDIT I tried to check the event logs and found the following warning. I do not know if this will be a question, will continue to dig now. Exception Information: Exception Type: HttpException Exception Message: Request Timeout.

+4
source share
3 answers

I would connect Visual Studio to IIS and break the debugger when a deadlock occurred. Then you can check the call stack of running threads.

The Code Project has a good article on how to perform remote debugging of IIS .

Of course, you can very well configure the test machine with local IIS and local Visual Studio .NET and do this without the need for remote debugging.

0
source
+2
source

If you use 'Failed Request Tracing' and it will produce a good output that will then tell you what is causing the error, down to the module level. This will then give you the first step to where it will break.

Read this article on iis.net → Troubleshoot Erroneous Queries Using Trace in IIS 7

+1
source

More articles:


All Articles