Error: Timeout expired.

Error: 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 am using window 2000 server and MS SQL 2K DEVELOPER.
i am doing .NET to connect to the server.

This error occur when there are too many ppl connect to the server.
May i noe how to solve/configure it.

thx in advance

As the error message states,your connection pool is full. YOu can either:

1. Increase the pool size, but I guess this will just solve the problem short-term :)
2. Do not use connection pool (not a good option)
3. See if you somehow leave connections open and don′t close it explicitly (which should be done within the scope thei are opened) Normally the garbage collector should and collect open connections, as far as I remember this is defined in the IDisposable Interface, but doing that explicitly will let you sleep better :)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||3. See if you somehow leave connections open and don′t close it explicitly (which should be done within the scope thei are opened) Normally the garbage collector should and collect open connections, as far as I remember this is defined in the IDisposable Interface, but doing that explicitly will let you sleep better :)

hmmm i cant IDisposable Interface. Can explain?
are there any sample web site where i can reseach about it? i have browse through google and yahoo but i cant find any information about this error.

thx

Error: Timeout Expired

I have an Update stored procedure that is used to update four tables at the same time. The issue is that it works perfect when i run the application in local server,but when i upload the application on to the server that is located in U.S, it gives an error "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."

I think the sqlCommand is timing out and the value is not returned. Is there a workaround to this issue? What could be the reason for this?

Any ideas.. Please help..

Do any of the tables you are tying to update have indexes on them? If not, adding indexes might help.

Ryan

|||How long will it takes to complete update on the local? Try to set the SqlCommand.CommandTimeout (default to 30 secs) to a larger value, as well as the SqlConnection.ConnectionTimeout.|||I haven't given any indexes.. But usually indexes are helpful when you perform a search on the data , rt? Will it help if while i update a table.. Im not sure.. could you give me more info on this? pls..|||I tried specifying the CommandTimeout to a larger value (4 minutes) and it still times out.. Is there a diff approach?|||

Developer_.NET:

I haven't given any indexes.. But usually indexes are helpful when you perform a search on the data , rt? Will it help if while i update a table.. Im not sure.. could you give me more info on this? pls..

Seehttp://www.odetocode.com/Articles/70.aspx.

Ryan