[erlang-bugs] Missing the tcp_closed event

[Mickaël Rémond]

Hello,

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 ?

-- 
Mickaël Rémond
  http://www.process-one.net/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20070413/8ab9bd0b/attachment.htm>