connection pool errors

  • Thread starter Thread starter Phil Townsend
  • Start date Start date
P

Phil Townsend

I have tried (apparently in vain) to correct the constant "connection
timeout error" in asp.net pages. We have switched to Applicatin Data
block, with little success. We have combed through all of our code to
make sure that datareaders are closed and resources deallocated and
still, we get the constant problem "connection timeout expired, etc." I
am beginning to believe this is either a problem with SQL Server, or a
bug in the .NET framework. Does anybody else have this problem? What
have you done to fix it?
 
Hi,

You can specify on your connection string the connection timeout time in
seconds, have you try it?

The other thing that happened to me with a webservice is that the function
expired and not my connection, to correct this I went to the Machine.config
file and change the following parameter:

executionTimeout

This parameters controls the amount of time that an asp.net function will
wait to execute, otherwise cancels the thread.

Hope this helps
Salva
 
Yes, and also there is a CommandTimeout setting that is independent of the
ConnectionTimeout.
You can set this on the Command Object. The SqlHelper class didn't have this
(latest versions may still not have it) and so long running queries would
time out even though there was no connection issue at all...
Peter
 
Back
Top