how does mTCP deal with zombie TCP connections? about mtcp HOT 3 CLOSED

mTCP expires those hanging connections if there is no activity for a certain period of time. That time could be configured by tcp_timeout in the configuration file.
If a connection expires, an error event will raised to the application. Then the application will close the connection after checking the connection is closed due to a TIMEDOUT event.

from mtcp.

Thanks. Is it possible to disable the tcp_timeout mechanism to have the longest possible connections? Or, if set to a really high number, can mTCP somehow reap the oldest inactive connection if too many connections get established?

from mtcp.

Setting tcp_timeout as -1 will disable the timeout check.
However, mTCP does not reap existing connections even if the number of connections reaches to its max value. I'm not sure if it's okay to kill such long-lived connections at the TCP layer.

from mtcp.