Last post Apr 11, 2005 02:15 PM by Redd
Apr 10, 2005 10:08 AM|eauderose|LINK
I used the CSK with IIS 5 in W2K with no problem. With my stand alone test platform W2003 SERVER with SQL 200O SP3 I have a "too much connections in the connection pool" error when I use it during about 5 minutes. I tried to change parameters in the connection
pool property in II6 with no success. I look for the code if in the CSK to see if some connection.close miss.
How can I locate the problem ?
Apr 11, 2005 02:15 PM|Redd|LINK
This is a known bug in the CSK. Unforunatly the post on the forums describing this was lost when ww.asp.net upgraded to forums 2.0 (a LOT of the fix details were lost this way).
Feel free to ask the www.asp.net team to restore the missing posts to the forum. I've asked, but have yet to hear back from them at all... but I figure if enough people complain then maybe they will restore ALL of the old
posts to the new forum here.
There were only a couple of places where datareaders were not closing their connections. The pattern, If I remember correctly, was that a utility method would be called to fetch a datareader. The returned datareader though did not have the close connection
behavior set. Most of the CSK doesn't return open datareaders, instead the called function itself uses the reader to populate some collection and the collection is returned instead of an open data reader. So you should be able to look for methods that retrun
data readers to locate potential sources of the problem.
This was fixed in GCN BTW, so perhaps a code comparison between the two will highlight which readers were changed.