Kerry Jiang
Kerry Jiang
Please help me confirm if you can.
It might be a SuperWebSocket compatible issue, the latest SWS broken the old API. I'll fix it ASAP.
Where did you get this error? Server side or client side? Do you have the exception's full stack trace?
From the error message, it looks like a server side issue. Probably you can get more details of this problem by tracing the network communication directly.
Please try WebSocket4Net latest beta release: https://www.nuget.org/packages/WebSocket4Net/1.0.0-beta.4
I thought this exception had been fixed long days ago?
Do it in your middleware: https://github.com/kerryjiang/SuperSocket/blob/master/src/SuperSocket.Server.Abstractions/Middleware/MiddlewareBase.cs
Thanks for the information, I'll have a test against this case.
我怀疑在你的场景下，发生了一下错误，然后listener就不再继续监听了。 //The listen socket was closed if (errorCode == 125 || errorCode == 89 || errorCode == 995 || errorCode == 10004 || errorCode == 10038) { break; }
@loveyeguo 出现这种情况的时候进程是不是挂掉了？ 我增加了log，建议从myget上拿最新代码重现这个问题，通过log再来找到导致这个问题的原因。