Open dreamlover opened 10 years ago
+1
+1
The same happens when I try to load test my websocket server written with ws.js
. I have no idea how to fix it, so about to switch to websocket-bench/socket.io which seems to be more handy to use.
I get a similar error, where it hangs on Progress. I see the open connection requests being made on my dev server. It never moves past this action. Not sure if its because its expecting an action on connection or if i'm missing components on my WebSocketServer implementation.
My WebSocket server (node.js + npm package: ws) just console.log out each message it received. When testing, the command line was always hung out with the last line is "Opened 100 connections", see the capture I attached.