Example not working about now HOT 8 CLOSED

Very interesting. Do you get this issue with other browsers?

from now.

The error was with firefox 3.6.10 and after testing I can say the nowjs
example does work with chrome.

After some idle time this is printed out at the server:

(node) warning: possible EventEmitter memory leak detected. 11 listeners
added. Use emitter.setMaxListeners() to increase limit.
Trace:
at Socket. (events.js:123:17)
at [object Object]. (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/client.js:83:20)
at [object Object]._onConnect (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/transports/xhr-polling.js:23:35)
at [object Object].check (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/listener.js:77:12)
at Server. (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/listener.js:33:14)
at Server.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1102:12)
at HTTPParser.onHeadersComplete (http.js:108:31)
at Socket.ondata (http.js:1001:22)
at Socket._onReadable (net.js:675:27)
(node) warning: possible EventEmitter memory leak detected. 11 listeners
added. Use emitter.setMaxListeners() to increase limit.
Trace:
at Socket. (events.js:123:17)
at [object Object]. (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/client.js:70:19)
at [object Object]._onConnect (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/transports/xhr-polling.js:23:35)
at [object Object].check (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/listener.js:77:12)
at Server. (/home/john/local/node/lib/node/.npm/
socket.io/0.6.16/package/lib/socket.io/listener.js:33:14)
at Server.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1102:12)
at HTTPParser.onHeadersComplete (http.js:108:31)
at Socket.ondata (http.js:1001:22)
at Socket._onReadable (net.js:675:27)

So this is probably a whole other issue.

from now.

Hey ubershmekel,

Can you try using the latest version of nowjs in Github/npm. We rolled out several crucial bug fixes that may or may not fix this issue. If you still have it with the latest npm version (v0.3.1) then I'll have a better idea of what is going on.

Thanks,
Eric

from now.

Hi Eric,

I was having the same issue as ubershmekel. I just npm'd the latest code and the original error has now gone away, but a new one has just presented itself. It is now possible to create one connection to the nowjs server, but not a second. Additionally, the first connection reports the following:

26 Mar 12:01:33 - socket.io ready - accepting connections
26 Mar 12:01:46 - Initializing client with transport "xhr-multipart"
26 Mar 12:01:46 - Client 3002093662507832 connected
Joined: Shane
26 Mar 12:01:48 - Initializing client with transport "flashsocket"
26 Mar 12:01:48 - Client 20963806682266295 connected
Joined: Shane

This results in each message sent to the server from the first client being duplicated in the messages container. I hope that helps!

Shane

from now.

Hey Shane,

What browser are you using?

Thanks,
Eric

On Sat, Mar 26, 2011 at 12:10 PM, swalkergibson
[email protected]
wrote:

Hi Eric,

I was having the same issue as ubershmekel. I just npm'd the latest code and the original error has now gone away, but a new one has just presented itself. It is now possible to create one connection to the nowjs server, but not a second. Additionally, the first connection reports the following:

26 Mar 12:01:33 - socket.io ready - accepting connections
26 Mar 12:01:46 - Initializing client with transport "xhr-multipart"
26 Mar 12:01:46 - Client 3002093662507832 connected
Joined: Shane
26 Mar 12:01:48 - Initializing client with transport "flashsocket"
26 Mar 12:01:48 - Client 20963806682266295 connected
Joined: Shane

This results in each message sent to the server from the first client being duplicated in the messages container. I hope that helps!

Shane

Reply to this email directly or view it on GitHub:
#21 (comment)

510-691-3951
EECS Student at UC Berkeley
http://ericzhang.com

from now.

Firefox 3.6.3 on Ubuntu 9.04

from now.

hi swalkergibson,

We have been able to reproduce the double connection bug and we're investigating thoroughly now. The cause is the name prompt window in the hello world example, it causes weird behavior because it blocks the javascript thread. This is a completely solvable bug and we'll be working on it.

Thanks,
Eric

from now.

Hey guys, the double connection issue has been reported here: socketio/socket.io#128

Closing now.

from now.