G
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.
"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.