I have no idea about the problem except that when using large number of clients, the main problem is having a ListenBacklog property with a small value. Default 5 is way too small for 1000 clients.
-- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "Paul" <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Thursday, April 20, 2006 8:09 PM Subject: [twsocket] HttpCli Statuscode = 0 > Hi, > > I've a stresstest program to test a new Http server. > There are 1000 clients logging on to the server. > These logons are handled in a continous thread that has to connect to a > Sql > server for each client. > After that , all clients are polling to this server, waiting for a command > and are answerred after about 20 sec. > When they first poll together, there are some clients that get an errocode > = > 0 and a statuscode=0, the latter should be 200. > On all subsequent polls, the statuscode is correct. > It's very hard to trap this error, as I don't know on wich client this > strange behaviour will occur. > > Is it possible that the 'keep-alive' time has been exceeded. > The logon for these 100 clients takes about 30 sec due to de database > operations. > > > Paul > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
