December 16, 2008 at 4:01 am
"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 get this error in management studio when I'm looking through SPs.
1. I open a SP
2. Check if I want to change the code
3. I close it
I have about 300 SPs to check, after a while I get this error. It seems like Management Studio is not closing the connections correctly.
If I run "sp_who2" I can see a lot of sleeping with my login.
All I have done is select "modify" on an SP and then closed the window it appeared in.
System information copied from Management Studio:
Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
Microsoft Analysis Services Client Tools 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )
Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 7.0.6001.18000
Microsoft .NET Framework 2.0.50727.3053
Operating System 6.0.6001
December 16, 2008 at 5:47 am
Make sure you close the connections once your work is done under them.
MJ
December 16, 2008 at 5:55 am
But I am working in Management Studio.
I open a SP with "modify" in the object explorer , a tab opens up containing the code for the SP, then I close the tab. This results in a sleeping thread.
I can't close it in another way.
What I'm saying is I just LOOK at the code in Management Studio, I'm not running anything. Right now for example I have 55 sleeping threads... They disappear when I close the whole Management Studio.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply