TCPView Showing TCP Connections Not Closing?

Hi All,

As most of you know, i do a lot of testing, i happened to notice a large number of TCP connections at the Close_Wait 2 status while hosting, so i did some testing,
TCPView shows what aplication has the unclosed connections, making testing easier.

using RSWCS , i noticed a large number of connections built up over night, i would often have anything from 800 to 2,800 of these not closed connections each morning,

using WCS, the same test over night built up between 800 to 2,800 unclosed connections each morning,

using FXS, testing over night i had less than 10 unclosed connections each morning,

using ZCS testing over night i had the odd 1 or 2 unclosed connections each morning,

i didn't test Ouka or Eagle's ES

the only explanation for the high number of them i can find is, possibly people in the room on secondary connection or Robo/WPCC that auto refreshes connections, and maybe the way that RSWCS & WCS connect, it maybe leaving the old connections not closed fully.

TCPView is a Free tool showing you TCP connections.

Hi Max,

Any chance of getting a screenshot pic of the tcp view for rswcs if poss if not all/any server please? Would love to resolve this in rswcs and having quickly whipped up the tcp for rswcs i have a vague idea whats causing this

Thanks,

well i opened an RSWCS Test Room last night, due to the fact i use ZCS for both current rooms,

there was no dead TCP connections this morning, i guess because there was only my RoboMx in it and my 2 Chat.Net's, there was only the 3 established connections from me,
nobody popped in, so as it had no users connected from outside, so it looks like it is to do with users from outside connections,

no point in a screen shot because all was normal, just 1 dead connection from my ZCS, the 1st one in 3 days and i have between 40-50 regs.

On a side note, the new RSWCS i'm working on appears to clear every tcp socket after use with none remaining. This includes cache connections, client connections and the server listening socket.

That is good news Richy, thanks.