Julio Barros
09/16/2020, 8:45 PMsocket.close()
and then socket.awaitClosed()
right after on the sockets instantiated by my server, the awaitClosed
function suspends forever. This happens especially when connections are already lost.
I did some investigation on the source code and found this TCPClientSocketOptions.socketTimeout
property, but it can only be set for client sockets. Is there some way of setting it on the server side? Is there an expected case in which calling socket.awaitClosed()
after close suspends forever?