Re: Why all the connections?
- From: "Lars Sondergaard" <sorry@xxxxxxxxx>
- Date: 30 Jan 2006 16:28:30 -0700
Hi
I have exactly the same problem and I have entered a QC for it for
Delphi 2005. The problem has been there since D5 and is still present
in Delphi 2006.
http://qc.borland.com/wc/qcmain.aspx?d=21073
I would be happy if I could persuade someone to vote for it and even
more happy if it could be fixed :-)
The problem is that Delphi is not enabling ADO connection pooling
correctly and since ADO version 2.3 (or 2.5 I don't remember) MS has
implemented that closed connections go into a TIME_WAIT state for a
certain period of time to prevent IP port high-jacking.
There is a KB article on the MS website describing how to enable the
pooling but even though I have tried to fix ADO.PAS several times I
have not had any luck with it. I guess this just shows why I don't work
at Borland :-), but I sure hope one of the smart guys there will find
the time to look at it.
In the QC I describe a work-around but this has to be applied to all
client PCs so it's a real pain and sort of a security risk that the
Security managers at our customer sites are often not willing to allow.
--
Lars Sondergaard
.
- Follow-Ups:
- Re: Why all the connections?
- From: Grant McAllister
- Re: Why all the connections?
- From: Vitali Kalinin
- Re: Why all the connections?
- References:
- Why all the connections?
- From: Kevin Davidson
- Why all the connections?
- Prev by Date: Re: ADO patch for D5? EOF BOF error.
- Next by Date: Re: TADOQuery.Open() & Sybase
- Previous by thread: Re: Why all the connections?
- Next by thread: Re: Why all the connections?
- Index(es):