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
This describes a likely cause for server hangs in some corner cases of race conditions.
It is possible for a client to initiate one or more client-side connections and then not call mainloop() on them. In some cases, this can result in the UDP packet asking the server to connect to a TCP port but then no servicing of the connection request. This can cause the server to hang, presumably waiting on the TCP connection request.
Even when the client calls mainloop() on one of the connections, the one that is not being mainloop()ed can keep hanging all of them.
The text was updated successfully, but these errors were encountered:
Either a timeout or a separate thread that signals timeout could be used to interrupt the hang, letting it retry again in a later loop. Or a separate thread could be spawned to establish the connection.
This describes a likely cause for server hangs in some corner cases of race conditions.
It is possible for a client to initiate one or more client-side connections and then not call mainloop() on them. In some cases, this can result in the UDP packet asking the server to connect to a TCP port but then no servicing of the connection request. This can cause the server to hang, presumably waiting on the TCP connection request.
Even when the client calls mainloop() on one of the connections, the one that is not being mainloop()ed can keep hanging all of them.
The text was updated successfully, but these errors were encountered: