1

I had some networking issues on my Windows server, and find out (by using NETSTAT) that I have more than 90,000 (!) connections in TIME_WAIT which didn't closed.

I've changed the TcpTimedWaitDelay param in registry, but apparently a server restart is needed. Because it's a single production DB server, I can't afford it at the moment.

Is there any way killing a TIME_WAIT connection? Any other suggestions?

Thanks! Roei

Roei
  • 319
  • 4
  • 15
  • Suggestion: ask questions related to networking and servers on superuser.com Stackoverflow is for programmer questions. – Lekensteyn Nov 18 '10 at 18:46

1 Answers1

1

I have more than 90,000 (!) connections in TIME_WAIT which didn't closed.

No you don't. These represent connections which have already closed, and whose local port is hanging around for TCP security reasons. They will only be that way for a couple of minutes each. Just wait.

user207421
  • 305,947
  • 44
  • 307
  • 483