Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 14:39:47 -0500
Ian Boyd wrote:
Just to be sure we're on the same page: the ConnectionTimeout "clock"
starts when the network services find the database server on the
network and provides a handle to the connection object. From what
I've read, the developer has no control over how long the network
services take to find and deliver the handle to the database server.
How are you forcing the timeouts to occur for your testing? And how
are you determining the point at which to start timing the "Actual
Timeout" period?
i am starting the clock just before i call Connection.Open.
Then you are not truly timing the ConnectionTimeout: you are timing the
amount of time it takes for the Connection to acquire a "handle" to the
database server plus the time it takes the ConnectionTimeout to time
out. Again, there is no control over the first part.
Original question stands.
I have seen this question (or variations thereof) asked many times in
the last 10 years and I have never seen a different answer. If someone
can provide one (I am certainly not omiscient), I will certainly be
interested in reading it.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- References:
- ADO ConnectionTimeout taking 2.3s rather than 1.0s
- From: Ian Boyd
- Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s
- From: Bob Barrows [MVP]
- Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s
- From: Ian Boyd
- ADO ConnectionTimeout taking 2.3s rather than 1.0s
- Prev by Date: Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s
- Previous by thread: Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s
- Index(es):
Relevant Pages
|
|
