Timeout expired

[Guest]

I recently deployed a new ASP.NET application. Since initial deployment we are consistantly having timeout issues. The browser clocks for several minutes and then this message is displayed:

"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 have done a fair amount of searching for a solution and have found very little that seems to relate to this problem. I did ensure that all of my database connections are being disposed in my code, as well as ensuring the application is being compiled to the release version rather than debug.

Does anyone have any idea what I might be missing? Is there a way to increase the "max pool size" ?

This application is running on our office wide intranet, so the number of users is very minimal. We are also running on Windows 2000 server.

 

[Guy]

Same problem here on a single user system using the "Data Access
Application Block for .NET v2" for all data access. Please post if
you find an answer. I saw someone suggest using datasets rather than
datareaders and will try that this afternoon.

 

[Guy]

Found this link at Microsoft. Will test it this afternoon:

http://support.microsoft.com/default.aspx?scid=kb;en-us;830118

Basically it syas to disable SQL debugging or switch from degub mode
to release mode. It also says that this is by design.