Hi Wilfried, thank you for replying.
How do i check how much non pageable ram is available?
The test i did for Windows Server 2003 runs on a
system with Xeon processor and 3gb ram. It
consistently stop at 180-200 concurrent clients which
is very strange compared to the other test that
accepts 500-600 concurrent clients on Windows XP with
single core processor and only 512mb ram.
The difference i notice on the Windows Server 2003
test were that the data being received is a lot faster
which makes me suspect that the main thread that
listen to clients are too busy pushing data to clients
and after a while the listening were timed out or
something like that?
Btw, after i diconnect all client i have check with
netstat -n -p tcp a few times and there's no socket in
WAIT_STATE at port 20000 which is the port the server
use and still the problem persist. It just won't
accept client anymore even Netstat -a shows the server
in listening state. See the following,
C:\Documents and Settings\edwardkoo>netstat -a
Active Connections
Proto Local Address Foreign Address
State
TCP Edward:http Edward.N2NMSC.COM:0
LISTENING
TCP Edward:epmap Edward.N2NMSC.COM:0
LISTENING
TCP Edward:microsoft-ds Edward.N2NMSC.COM:0
LISTENING
TCP Edward:gds_db Edward.N2NMSC.COM:0
LISTENING
TCP Edward:3389 Edward.N2NMSC.COM:0
LISTENING
TCP Edward:20000 Edward.N2NMSC.COM:0
LISTENING
TCP Edward:58581 Edward.N2NMSC.COM:0
LISTENING
TCP Edward:1059 Edward.N2NMSC.COM:0
LISTENING
C:\Documents and Settings\edwardkoo>netstat -n -p tcp
Active Connections
Proto Local Address Foreign Address
State
TCP 127.0.0.1:1089 127.0.0.1:1090
ESTABLISHED
TCP 127.0.0.1:1090 127.0.0.1:1089
ESTABLISHED
TCP 127.0.0.1:1091 127.0.0.1:1092
ESTABLISHED
TCP 127.0.0.1:1092 127.0.0.1:1091
ESTABLISHED
TCP 127.0.0.1:1276 127.0.0.1:9000
ESTABLISHED
TCP 127.0.0.1:9000 127.0.0.1:1276
ESTABLISHED
TCP 192.168.0.136:1106 202.75.55.43:2888
ESTABLISHED
TCP 192.168.0.136:1275 192.168.0.136:3050
ESTABLISHED
TCP 192.168.0.136:1304 192.168.0.11:135
TIME_WAIT
TCP 192.168.0.136:1305 192.168.0.11:1026
TIME_WAIT
TCP 192.168.0.136:3050 192.168.0.136:1275
ESTABLISHED
I made a button that will close the listening socket
and re-listen so when the problem occurs i click the
button to test. After i click the button the listening
will work for a while and then it will eventually stop
again.
I already tried catching OnBgException but it does not
trigger even though the problem occurs.
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=list&sid=396545433
--
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
