|
Subject:
|
Find open DB Connection again
|
|
Posted By:
|
Ron Howerton
|
Post Date:
|
4/23/2008 10:29:46 AM
|
Sorry to repost this, but the response I got did not answer the question and somebody who might have an answer could skip the question as it appears to have gotten a response. Nor did I get an email indicating I received a response despite subscribing to the topic, if anybody from P2P is reading this.
Anyway, I am still randomly getting this error every few days:
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
I don't wish to increase pool size or turning off pooling as those don't really fix the problem. And I don't need advice on how I should've coded it. I just need to find the leak.
Is there any way to figure out which connection(s) are being left open? There is a lot of code to be checked, so randomly searching for this problem is unlikely to find it, and a trace could potentially turn up hundreds of DB calls that would be as painful to search as the code itself. Are there any tools or techniques that can help me quickly find where in my code connections are being left open?
|
|
