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
It seems there's a small time frame when the remote server may ignore the just received incoming operation request, thus blocking the client application (which is synchronously waiting for a reply packet). The listener thread is still operational in this case.
It's really hard to reproduce, the only known condition is that the client application should send packets with an interval of 60 seconds which corresponds to a timeout to shutdown the inactive worker thread. Reported against Classic, but SuperServer may also be affected.
Submitted by: @dyemanov
It seems there's a small time frame when the remote server may ignore the just received incoming operation request, thus blocking the client application (which is synchronously waiting for a reply packet). The listener thread is still operational in this case.
It's really hard to reproduce, the only known condition is that the client application should send packets with an interval of 60 seconds which corresponds to a timeout to shutdown the inactive worker thread. Reported against Classic, but SuperServer may also be affected.
Commits: 25957ce c122909
The text was updated successfully, but these errors were encountered: