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 |
|
jackstow
Posting Yak Master
160 Posts |
 Posted - 2002-03-22 : 10:20:09
|
I have a .NET/SQL 2000 website that has been running like a greyhound all through development but has suddenly started erroring with timeouts quote:
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.
.. it then comes back up and runs fine for a while until it times out again. There are only ever 2 or 3 users (developers) on the site. Any ideas? |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-22 : 10:25:18
|
| Sounds like connections are not being fully closed. Try running sp_who or sp_who2 when you get a timeout and see how many are open on the server.Edited by - robvolk on 03/22/2002 10:25:46 |
 |
|
|
jackstow
Posting Yak Master
160 Posts |
Posted - 2002-03-22 : 10:42:21
|
| Thanks - I like those procs. One question - when I run it I can see around 80 connections open for the .NET app, but only one for each of the standard ASP sites running on the server - is there something suspicious there? |
|
|
|
jackstow
Posting Yak Master
160 Posts |
Posted - 2002-03-22 : 11:03:03
|
| Ok here's the scenario now - the site has timed out again, ran sp_who2 and there are 118 connections 101 of which are for the .NET site - there is one connection for a ASP site on the same server and that site is still running... Is this an ADO.NET problem? |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-22 : 11:06:51
|
| ADO.NET is an ENTIRELY different animal from regular ADO, I think you know this already but just to make sure. I'm not versed in ADO.NET at all really, but the concept of connections, commands, etc. is completely different. I think that if you kinda moved ASP/ADO code to a .Net app without making radical changes to it, it might be the cause of the problem.Take some time looking through the ADO.NET documentation, and also look at ASP/ASP.Net sites for some more information:www.4guysfromrolla.comwww.asp101.comwww.15seconds.comwww.aspalliance.comAnd check out any favorite sites of yours I haven't listed here! I believe there was an ADO.NET primer on at least one of these 4 sites, they detailed very nicely some key differences/changes. |
|
|
|
jackstow
Posting Yak Master
160 Posts |
Posted - 2002-03-22 : 11:18:43
|
| Yeah I realise that ADO.NET is quite a distinct genus from ADO - the .NET website was/is built with ASP.NET from the ground up, using all the recommended coding principles, so it should be OK. BTW my fav .NET site is www.gotdotnet.com . Maybe we could do with an ADO.NET forum here at SQLTeam ?? - Oh the .NET site just came up again (!?) strange... |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-22 : 11:33:08
|
quote:
Maybe we could do with an ADO.NET forum here at SQLTeam ??
It would be a great idea IF IF IF you can guarantee we won't get a flood of "I need to write an e-commerce site in ASP/ASP.Net, please help" questions! (unless you want to answer them all!) And you've seen how many posts we get where the answer is in Books Online, or on the SQL Team home page(!) or FAQ.Unfortunately, we answer far too many ASP/ADO questions already. 90% of them are timeout problems, and 99.9999999999% of THOSE are due to Do While Not rs.EOF...rs.MoveNext...Loop usage. I don't have stats on this but it wouldn't surprise me if even 50% of our posts and replies fit this description. I love all the business, really I do, but at some point we'd end up with 1 or 2 real SQL Server posts a day.My 2¢ |
|
|
|
|
|
|
|
|
Timeout