How do I debug a connection leak in an ASP.NET 2.0 Web Services application?
I have an application that is a collection of C # web services sitting on top of ASP.NET 2.0 in IIS7 on Win2k3. After the latest version, we keep getting connection timeouts. A quick investigation using Perfmon confirmed that our application is a connection leak.
However, there were so many code changes in the latest release that it is really difficult to determine where the problem is just by looking at the code changes.
Is there a way to debug when connection leaks actually occur?
a source to share
You can use performance counters to check for memory leaks.
See this link: http://msdn.microsoft.com/en-us/library/fxk122b4.aspx
Can you tell if your application has memory leaks or not? But it won't find the code that calls this. To do this, you need to debug your application.
a source to share