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
Start two sockets and connect them.
{code:erlang}
{ok,S}=gen_sctp:open(6666).
gen_sctp:listen(S,true). {code}
{code:erlang}
{ok,C}=gen_sctp:open().
gen_sctp:connect(C,localhost,6666,[]).
{code}
{{Loop over a call to recv (with timeout).}}
{code:erlang}
RECV = fun(G,Sck) -> io:fwrite("~p~n",[gen_sctp:recv(Sck,500)]),G(G,Sck)end.
Pid = spawn(fun() -> RECV(RECV,S) end).
{code}
Close the socket.
{code:erlang}
gen_sctp:close(S).{code}
The socket and the recv process is now stuck forever.
{code:erlang}
process_info(Pid,current_function).
{current_function,\{prim_inet,recvfrom0,3}
{code}
The text was updated successfully, but these errors were encountered:
Alas this is not a high priority for Ericsson, but we will try to find some time to look into it. Can not make any promises on when that will be though. Any insights anyone might have on this issue are more than welcome.
Hi,
The bug seems to be in the socket close. It does to inform those processes that have
ongoing requests towards the socket (port). Thereby leaving the process hanging.
This effects both udp and sctp since they share this code.
Regards,
/BMK
Original reporter:
massemanet
Affected version:
Not Specified
Component:
erts
Migrated from: https://bugs.erlang.org/browse/ERL-1242
The text was updated successfully, but these errors were encountered: