Hello Edward, Possible you ran out of buffer space. Winsock use non pageble ram. The non pageable ram can grow to max 1/8 the size of total ram. Depending on traffic each socket need about 6 KB of it. And lots of other applications uses that part of RAM also (all overlapped IO for example).
After all clients are disconnected you possible have all sockets still in WAIT_STATE. That can be the reason. Also be sure you hvae code in OnBgException and set CanClose to true. In OnSessionClosd you can post a message to a custom message handler to listen again. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz Wednesday, September 12, 2007, 07:05, Edward Koo wrote: > Hi, > I wrote a server with TWSocket that receive high speed > data and then push the data to connected clients. I > did some stress test recently and found that the > server will stop accepting client after it reach > something like 500-600 concurrent clients on Windows > XP and only about 180-200 on Windows Server 2003!? > Any client attempts to connect at this point will get > a socket error 10061, this happen even if all the > previous clients are disconnected. A breakpoint to the > code shows that SocketSessionAvailable will not > trigger anymore. It's like the server listening socket > is closed but I checked with Netstat -a and it shows > that the server is still listening to the designated > port. > I tried to change WSocket_listen backlog to 200 but it > won't help also. Any idea? > ____________________________________________________________________________________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, > news, photos & more. > http://mobile.yahoo.com/go?refer=1GNXIC -- 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
