Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Say a client opened a TCP connection to my server. We send some data back and forth, and eventually my server closes the connection. However, due to a bug in the client's software (perhaps at a low level), it doesn't realize the connection has been closed and continues to try to send data to the server.

How much of a performance impact will this have on my server?

share|improve this question

closed as not a real question by David Schwartz, rnxrx, Ward, Scott Pack, HopelessN00b Oct 1 '12 at 23:28

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Is it trying to send the data with the pre-existing session, or does it re-establish or try to establish a new TCP connection and does your server permit it to do so? I agree with Michael Hampton's answer but wonder if the client is "taking the hint" or not. (This is more for debugging their software, I guess) – TheCleaner Sep 20 '12 at 21:17
Are we talking about a TCP stack bug or an application bug? – David Schwartz Sep 20 '12 at 21:43

Very little impact on performance, though it will consume bandwidth.

IF the traffic reaches your server, it'll just get rejected out of hand since it doesn't correspond to an open connection.

Your edge firewall may also drop it for you, since it doesn't correspond to an open connection.

share|improve this answer
+1 for edge firewall. – msanford Sep 20 '12 at 21:17

Not the answer you're looking for? Browse other questions tagged or ask your own question.