Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
amsqlguy
Yak Posting Veteran
89 Posts |
 Posted - 2010-03-19 : 09:08:07
|
| Guys,I am trying to troubleshoot connection pool max out issue. Below is the error we are getting "The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and maxpool size was reached."Towards troubleshooting this error is it safe to assume that each SPID fromthe activity monitor is a unique connection from the application and that eachof these SPIDs contribute towards the connection pool.Any suggestions/inputs would help.Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2010-03-19 : 19:40:21
|
| If you aren't specifically setting the connection pool size, it defaults to 100. This is usually more than enough. If you are exhausting the pool, the most likely suspect, to me, is that you have a coonection leak or some process is holding a connection open longer than is reasonable. you could run exec sp_who2 to see if the LastBatch date indicates anything funky.=======================================There are no passengers on spaceship earth. We are all crew. -Marshall McLuhan, educator and philosopher (1911-1980) |
 |
|
|
|
|
|
Connection Pool max out