Can we forcibly close TCP connections in FIN_WAIT2 state?

Solution Unverified - Updated -

Issue

Is there a way to force the closure of FIN_WAIT_2 sockets left around for a long time?
When the application stack is large, if any 3rd party applications trigger this kind of situation of accumulating FIN_WAIT_2 sockets, how can we deal with it promptly without the need to restart the application?

Environment

  • Red Hat Enterprise Linux (all versions)

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