March 19, 2010 at 7:09 am
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 max
pool size was reached."
Towards troubleshooting this error is it safe to assume that each SPID from
the activity monitor is a unique connection from the application and that each
of these SPIDs contribute towards the connection pool.
Any suggestions/inputs would help.
Thanks
March 19, 2010 at 8:15 am
the connection pool is client side.
afaik by default the connection pool size is 100 connections.
You can monitor it using windows perfmon.
At sqlserver level you can get an overview of pooled connections as well.
"How To Tell: If connections to SQL Server are pooled (or not) "
edited:
maybe also have a look at "The .NET Connection Pool Lifeguard"
http://msdn.microsoft.com/en-us/library/aa175863%28SQL.80%29.aspx
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
March 19, 2010 at 8:31 am
In the connection string just add "Max Pool Size ="..
I would personally look at the application that is setting/creating pool size. In my experience it has been the application not closing to connection properly.
If you do increase the pool size, keep an eye on the memory. In my case it was a web server app that was not clearing the connection, the dev increase to pool size (as temp measure) therefore the memory increase dramatically!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply