Denial of Service Bug

bob123 · Post by **bob123** » Fri Sep 08, 2006 12:24 pm

We have experienced a denial of Service to SOS as a result of resources being used up from bogus Established TCP socket connections. These connections once existed, but the end users did not close the connection gracefully, by shuting down SOS. This eventually left over 2 dozen Established connections that really no longer existed. Using TCPview from Sysinternals, I closed all of the Established sockets to SOSsvr.exe on port 8888, and then I was able to connect to SOS again.

Does anyone have information on this potential bug?

I have VSS 6.0c and SOS 3.5.2 installed on Windows Server 2003 STD SP1 on a P4 2GHz desktop computer.

Beth · Post by **Beth** » Fri Sep 08, 2006 3:09 pm

What should take care of that is go into the SOS Server Manager - General and set the timeout idle connections.

bob123 · Post by **bob123** » Tue Sep 12, 2006 11:23 am

I set the timeout to 5 minutes and restarted SOS. I recreated the orphaned Established sockets, but they remain Established after 90 minutes.

Beth · Post by **Beth** » Tue Sep 12, 2006 1:46 pm

I'm not sure how it would handle the ones that were there previously. Are any new ones popping up? If so, then I'd just suggest getting rid of the old ones and see what it does with new ones.

Beth · Post by **Beth** » Wed Sep 13, 2006 12:34 pm

Can you double check that you don't have the Keep Alive option set? That is found in the client under Tools-Options and then on the General tab. If that is set, it is probably conflicting with the Close Idle Connections.

SourceGear Support

Denial of Service Bug

Denial of Service Bug

It sounded like it should have worked...