Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No responding! #5

Open
dreamlover opened this issue Jul 12, 2014 · 4 comments
Open

No responding! #5

dreamlover opened this issue Jul 12, 2014 · 4 comments

Comments

@dreamlover
Copy link

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.
thor_error

@mkozjak
Copy link

mkozjak commented Mar 10, 2016

+1

1 similar comment
@qualifyapp
Copy link

+1

@oleggromov
Copy link

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.

@kingthrillgore
Copy link

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.

screen shot 2017-12-21 at 1 11 26 pm-mod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants