🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:41e63652$1@newsgroups.borland.com...
>
> You said that you are using ICS.  ICS does not use separate threads for
each
> connection.  Even if it did, though, the server has to call accept() first
> for each connection, and that occurs in a different thread than the ones
> that are created to service the clients after they connect.  My earlier
> comments still stand.
>
I have some new findings on my problem.  I examined the Win2k event log and
found:

Error EventID 2020: The server was unable to allocate from the system paged
pool because the pool was empty.

Using Win2k Task Manager to monitor the application again I found that the
paged memory pool kept growing, and the number of handles allocated to the
application never decreased.  I stepped the client thread execution again
and was sure it called its destructor upon termination, and this in turns
called ICS TWSockt's destructor:

__fastcall TClientThread::~TClientThread()
{
   :
   :
  if(FClientSocket != (TWSocket *)NULL)
  {
    FClientSocket->~TWSocket();
    FClientSocket = (TWSocket *)NULL;
  }
}

In ICS source WSocket.pas there is a method
TCustomWSocket.DeallocateSocketHWnd.  I can see this is called when stepped
in BCB.  And handles can be released.  I am not familiar with the Delphi
source.  Can you see possible areas that can inhibit handles to be released
during loading test (many client requests are generated simultaneously)?

Regards,
Patrick