[erlang-bugs] Missing the tcp_closed event
Fri Apr 13 17:43:08 CEST 2007
We feel that under hard to reproduce conditions (production system
with ten of thousands connected users), the Erlang TCP module can
miss the tcp_close event.
The process is receiving event in active once mode. It is not stuck
in a send.
It seems to happen with the new Erlang R11 in SMP mode.
The port is in a enotconn state, but the process has not been
informed that the tcp connection has been closed.
Has anyone the same feeling ?
Any idea how to debug that possible problem ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-bugs