What happened to me and WebSocket (a)

My scheming big guy quit, before he go I did not solve good one problem, feel if I change the job interview, others asked "You in the project, the most headaches encountered in the problem is what, how to solve?" "The first thought should be him, and today it feels like it's time to write something up."

Do Pmgo, Tao elder brother proposed to use the browser desktop push, to replace HX reminders, the first proposed websocket idea, actually not our group, other group also useful, but can not learn, big guys are node. js implementation, with Nginx do reverse proxy to deploy it, I only Iis,.net support WebSocket seemingly also not too distant things, at that time to consider using, there is not much to learn from, and later found on Github Fleck (Https://github.com/statianzo/Fleck), Although not the most fork, but the most convenient to use, for the internal system, regardless of the maximum number of connections, it is quite useful (not that it does not support but there are some problems, refer to issue)

The code was written out, it felt very refined, and then we went online.

After the formal service update is still very stable, then we intend to do on this basis to do iterative kanban real-time updates. About one months later, the test WebSocket reported an exception, "The current port is occupied", I began to think that the update test suit, the client and the server connection is not broken in time, the port resources were seized in the case can not be used again to do the same port service, so I waited for a moment to try to open the service, Can be successfully started, nothing. That's what I've been ignoring. One months later, even though a small number of port occupancy errors occurred during this time, the service could no longer be started, no matter how long it took.

I apply for a server, find the process ID of the port, use the PID to the task Manager to find the corresponding process, not found. Tasklist|findstr find the corresponding port process status, found a lot of time-wait process, the corresponding PID is just found. Helpless intranet can not be a souvenir, I will treasure it ...

Looking at his issue, one of the authors mentioned the connection bottleneck, but it seems to be an SSL certificate problem, so I fell on the pit ...

What happened to me and WebSocket (a)