Large number of CLOSE_WAIT sockets seen in "netstat" or "ss"

Solution Verified - Updated -

Issue

  • Large number of CLOSE_WAIT sockets seen in netstat or ss
  • When running an application, it's possible that the application may produce a socket in CLOSE_WAIT state from a state such as ESTABLISHED or TIME_WAIT.
  • What does this state signify, and how can it be adjusted?
  • If I have an application with many of these sockets, what are the implications of this?
  • Getting close wait connections on Service mix server. We have observed close wait socket connections on windows server and as per discussion from windows and network team we have found that it’s an application side issue and it was closing connections:
  • Port 8081 running “JAVA.exe” has CLOSE_WAIT sockets.
  • How to Kill Or Reduce TCP Close_Wait connections?
  • Is there a way to terminate the tcp close_wait sessions in Linux ? In general, they go away automatically on its own . But is there a way to Speed up this process ?
  • Why there are many 'CLOSE_WAIT' sockets seen in "netstat" command output ?
  • When running netstat command there are many CLOSE_WAIT state sockets.
  • Sockets are seen in this state even after the default of TCP connection timeout.

Environment

  • Red Hat Enterprise Linux
  • TCP (Transmission Control Protocol)

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