Thread: Timeout error

We generally get this error in our .NET 2.0 web app.

error connecting: 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.

Site is hosted on GoDaddy, and i must say that this happens on GoDaddy only. Anyway, i added this in my connection string

Code:

Pooling=true;Max Pool Size=100;Connection Timeout=60;

Still doesnt seem to work

Any advise??

Micky

What happens if you increase timeout to 900?

Originally Posted by jmurrayhead

What happens if you increase timeout to 900?

Seem to work good now

Is there any drawback in increasing time out and pool size??

Well, this doesn't fix the problem of the connection actually taking so long. I would look into optimizing the database, caching, and such. Particularly on a shared hosting account...the number of users accessing the database could easily overwhelm it.

Actually, the same thing replicated on our test servers/site; works fine.

Not many users also.

As i said, i have seen/faced this problem on GoDaddy only

Is there any app/software that can check if there is any connection leak or tell me if where is the problem in code, if there is??