Why are both ends of a TCP connection in the TIME_WAIT state?

Solution In Progress - Updated -

Issue

  • Both sockets on 2 different machines are in the TIME_WAIT state. Which is holding the tuple up for an extended period of time approximately 60 seconds so it's unable to be reused.

Environment

  • Red Hat Enterprise Linux
  • TCP

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content