views:

134

answers:

1

I have an app, which is a bunch of c# web services sitting on top of ASP.NET 2.0 in IIS7 on Win2k3. Following the last release, we keep getting connection timeouts. A quick investigation using Perfmon confirmed that our application is leaking connections.

However, there have been so many code changes in the last release, that it is really difficult to determine where the problem is just by looking at code changes.

Is there a way to debug where the connection leaks are actually occurring?

+1  A: 

You can use performance counters to check the memory leaks.

See this link: http://msdn.microsoft.com/en-us/library/fxk122b4.aspx

It can say whether your application is having memory leaks or not? But it will not find the code which is causing that things. For that you have to debug the application.

jalpesh