Skip to end of metadata
Go to start of metadata

TCP connections with the status FIN_WAIT_2 are those, which are not closed correctly with shutdown(). This maybe caused by JobScheduler, but normally it sends the shutdown() command to close the connection finally.

Propably it is a problem of the browser, but after 120sec in FIN_WAIT_2 state the connection will be closed anyway.

There is no way for JobScheduler to manipulate this behaviour.

see also: What is a FIN_WAIT state?

Write a comment…