Hello Dale,
I have never received this error, but it sounds to me like you have created
an object that you are storing in a static list, and that object contains a
connection to a database, and you are opening the connection but never
closing it. After a while, you cannot reconnect to the database because you
have used up the available connections in the connection pool.
Please understand that there is no reason to keep a connection around at
all. .NET will handle the caching for you. Simply open a connection, use
it, and close it. If you are using C#, take a look at the "With" keyword.
It makes error handling much easier.
Realize that I am guessing. I may be completely off base. You have not
provided enough information for me to be accurate. If I am wrong, I would
be best able to provide useful input if you would give more details about
your application. What does your app do? On what statement or call is this
error appearing? Can you post a snippet of code where you are getting the
error?
--- Nick
"Dale Hersh" <dalehersh@-NOSPAM-hotmail.com> wrote in message
news:OQ**************@tk2msftngp13.phx.gbl...
Hi Everyone,
I have been using .net for a few weeks and I am getting the following two
errors:
1.
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.
2. Network Connection Error
I am not sure how to get around these problems and this error does not
occur everytime I use my apps. It seems to be sporadic, but does occur quite
frequently. Any help would be greatly apprecaited...
Thx.
Dale
---
Posted using Wimdows.net Newsgroups - http://www.wimdows.net/newsgroups/