You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some network conditions which may lead to connection being stuck in Fin_Wait2 state in defintley which is causing submit_sm to not be sent to the upstream.
$ cat /proc/sys/net/ipv4/tcp_fin_timeout
60
The kernel timeout only applies if the connection is orphaned. when the connection is still attached to a socket, the program that owns that socket is responsible for timing out the shutdown of the connection. The question is there a way to set fin_wait2 timeout on the application side to clean up the if the connection is stuck in this state for more than 60 seconds ?
The text was updated successfully, but these errors were encountered:
There are some network conditions which may lead to connection being stuck in Fin_Wait2 state in defintley which is causing submit_sm to not be sent to the upstream.
The kernel timeout only applies if the connection is orphaned. when the connection is still attached to a socket, the program that owns that socket is responsible for timing out the shutdown of the connection. The question is there a way to set fin_wait2 timeout on the application side to clean up the if the connection is stuck in this state for more than 60 seconds ?
The text was updated successfully, but these errors were encountered: