November 19, 2015 at 10:38 am
... but I didn't know who else to turn to. 🙂
We have a web application that recently started throwing "Connection Timeout... connection pool" errors daily. The traffic on the site is comparable to other days. We've been checking the sysprocesses table and have been watching the connections range from 2 - 85. As expected in quiet times the connections are reclaimed. Most of the time the connections are listed as sleeping. We're using the default 100 connections.
My question is, even if we hit 100 connections, if they're sleeping they should be available in the connection pool, right? I'm thinking that the issue isn't that a connection can't be made, but that something else is happening to cause the timeout.
Any thoughts?
We've increased the connection pool to 200 but I feel it's shooting in the dark.
Thanks
ST
November 19, 2015 at 12:30 pm
souLTower (11/19/2015)
... but I didn't know who else to turn to. 🙂We have a web application that recently started throwing "Connection Timeout... connection pool" errors daily. The traffic on the site is comparable to other days. We've been checking the sysprocesses table and have been watching the connections range from 2 - 85. As expected in quiet times the connections are reclaimed. Most of the time the connections are listed as sleeping. We're using the default 100 connections.
My question is, even if we hit 100 connections, if they're sleeping they should be available in the connection pool, right? I'm thinking that the issue isn't that a connection can't be made, but that something else is happening to cause the timeout.
Any thoughts?
We've increased the connection pool to 200 but I feel it's shooting in the dark.
Thanks
ST
You almost certainly have some rogue code somewhere that is not properly disposing of the connection object. The connection must be release back to the pool before it can be reused. What you are describing is the classic symptom of not releasing the connection.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 20, 2015 at 4:07 am
But the system has been operational for 1 1/2 years without throwing this error. The load has not changed dramatically. In the past week a number of MS Server patches and a symantec update have been installed on the servers (Win2008R2, SQL2008R2). The application code has not changed in this time.
When watching the number of connections I see it increasing and decreasing as I would expect as the pool manages itself. I don't disagree that there could be a connection that's not being closed but would that appear differently when looking at the sysprocesses data or would it also be listed as sleeping?
Thanks for the response
ST
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply