Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Maximum pool size
Message
From
01/10/2010 10:48:54
 
 
To
01/10/2010 02:36:12
Neil Mc Donald
Cencom Systems P/L
The Sun, Australia
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01483453
Message ID:
01483493
Views:
26
>See http://dotnetdebug.net/2007/04/04/systeminvalidoperationexception-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/
>
>or
>
>http://www.15seconds.com/issue/040830.htm

I read the second link. They suggest to close the connection as we use it. From a Web site, I always thought the optimized way was to open the connection when the hit starts and closes it when the hit is completed. Based on their example, if I would have 40 SQL requests on the hit, to return a Web page, this means I would have to open the connection 40 times and close it 40 times. Is this how your understand it?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Reply
Map
View

Click here to load this message in the networking platform