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

Socket.io dies (uncatchable) on faulty web socket connection #44

Closed
cramforce opened this issue Sep 3, 2010 · 5 comments
Closed

Socket.io dies (uncatchable) on faulty web socket connection #44

cramforce opened this issue Sep 3, 2010 · 5 comments

Comments

@cramforce
Copy link

Streamie.org was crashing constantly with a message that in line 23 of websocket.js this.connection did not have a method of "setTimeout"

Because this was the production system I added a line
if(!this.connection.setTimeout) return;

This works around the server-crash issue for me.

I now get this constantly
3 Sep 14:31:07 - Initializing client with transport "websocket"
3 Sep 14:31:07 - WebSocket connection invalid

I suspect a faulty client is reconnecting all the time.

@rauchg
Copy link
Contributor

rauchg commented Sep 3, 2010

Fix for certain buggy clients. Needs more investigation. Thanks Malte Ubl (@cramforce) for the report. Closed by 701c35d

@dshaw
Copy link
Contributor

dshaw commented Sep 24, 2010

Still getting this in 0.5.3.

Here's a copy of the error:
/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:23
this.connection.setTimeout(0);
^
TypeError: Object # has no method 'setTimeout'
at [object Object]._onConnect (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:23:18)
at [object Object]. (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/client.js:17:7)
at new (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:7:9)
at [object Object]._onConnection (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:123:73)
at [object Object].check (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:83:9)
at Server. (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:39:12)
at Server.emit (events:27:15)
at HTTPParser.onIncoming (http:831:10)
at HTTPParser.onHeadersComplete (http:87:31)
at Stream.ondata (http:763:22)

@dshaw
Copy link
Contributor

dshaw commented Sep 24, 2010

FWIW, http://github.com/dshaw/canisocket/ is running with @miksago's node-websocket-server without issue. http://canisocket.com/

Perhaps that will help triangulate the issue.

@rauchg
Copy link
Contributor

rauchg commented Sep 24, 2010

It was fixed in master

@dshaw
Copy link
Contributor

dshaw commented Sep 25, 2010

Great, thanks Guillermo. Switched to master and http://github.com/dshaw/remoteconsole is working great.

darrachequesne added a commit that referenced this issue Jul 4, 2024
- Remove deprecated iOS 7.1
- Add Firefox and Microsoft Edge browsers
- Add latest stable Node.js release
darrachequesne pushed a commit that referenced this issue Jul 8, 2024
Bump dependencies, update package.json and travis settings
darrachequesne added a commit that referenced this issue Jul 8, 2024
This issue was closed.
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

3 participants