How I broke the TCP Stack
time to read 1 min | 188 words

Today I spend a large part of the day tracking down various strange errors. Those errors would be of the following variety:

  • The connection could not be made because the target machine actively refused it.
  • A connect request was made on an already connected socket.
  • The underlying connection was closed: A connection that was expected to be kept alive was closed by a server.

Now, I am not doing anything strange with TCP/IP, I am just making plain old web service calls (and no, not using my hand rolled SOAP stack).

I can't really figure out what is going on, but I know that the problem is no in the TCP/IP level, it is something in my code, that is breaking things. It doesn't happen always, but it happens often enough.

I have ensured to my satisfaction that the server it up, no firewall in the way, respond to calls, etc.

Flat out weird, and I am not looking forward to trying to figure it out tomorrow.

Any ideas?

0 comments
Tags:

Related posts that you may find interesting:

23 Feb 2021 Didja know: Network failure due to the disk full error
programming bugs raven ravendb.net +1
21 Jul 2008 [Unstable code] How a blocking remote call can take down an application
Bugs Debugging Design
02 Feb 2016 Production postmorterm: Houston, we have a problem
raven production bugs