Socket.IO not falling back on "long-polling" on Heroku instance?

[jaypeeZero]

I opened a ticket with Heroku about a Socket.IO example not working on a brand new instance. This is what I sent them:

I uploaded a quick test to try out some things on Heroku and using one of the examples from the Socket.IO website, it doesn't >work. I looked at the logs and I see

setting request GET /socket.io/1/websocket/90084221689769639
set heartbeat interval for client 90084221689769639
then
websocket connection invalid
transport ended

The example works on my local machine and an Amazon EC2 instance perfectly, but I will need Heroku for the Node Knockout competition.

Heroku's response was:

Socket.IO is trying to use websockets, which we don't support; shouldn't it fall back to http 1.1 long-polling though?

So my question is why is Socket.IO NOT fallling back on Long-Polling? Do I need to do something in the code to make it work?

[3rd-Eden]

Which version of Socket.IO are you using?

[jaypeeZero]

For Heroku you have to provide the version through your package.json file so I can only verify (for now) that my file says "socket.io": "0.7"

[3rd-Eden]

I'm asking this because the connectTimeout didn't work at all for < 0.7.6. I fixed it in 0.7.7. so if you update it should probably work. crosses fingers :)

[jaypeeZero]

Winner! Changed my package.json to "socket.io": "0.7.7" and it works!

EDIT: I spoke too soon. It now connects, but the connection doesn't stay alive very long and then it will no longer reconnect. I'm working with Heroku to figure this out but if anyone has any insight let me know.

[jaypeeZero]

Thanks to Heroku support folks I found this solution:
io.configure(function () {
io.set('transports', ['flashsocket', 'xhr-polling']);
});

It appears to be working fine in Chrome. However, Internet Explorer 8 doesn't work. It receives information but does not send information, and then it disconnects and won't reconnect.

[jaypeeZero]

It looks like with IE 8, it is getting the connection, and for a time (a minute tops) works correctly, then it stops Sending information (but still keeps receiving it), then after another another minute or so it disconnects and won't reconnect.

When looking at my Heroku logs I see:

close timeout for client.....
xhr-polling closed due to exceeded duration
setting request GET /socket.io/1/xhr-polling/.....
setting poll timeout
discarding transport
cleared close timeout for client......

At which point IE is no longer able to reconnect unless the page is refreshed.

My transports are set up like this:
['flashsocket', 'xhr-polling', 'json-polling']

I would prefer to use the fastest possible first, does the order they are placed in the list matter?

[edwardhotchkiss]

I had the same issue. The code below works fine for me now in terms of no errors crashing the app on Heroku. The other issues are speed (ugh) & running it as a non-privileged local user on my development machine brings up the debug warnings: "unable to listen to port 843 as your node.js instance does not have root privileges. the flash policy file requests will only be served inline over the supplied http server. inline serving is slower than a dedicated server instance.
" related to the speed issue before.

io.configure(function() { io.set("transports", ["xhr-polling", "flashsocket", "json-polling"]); });

[jaypeeZero]

The issues with Heroku have caused me to move to Joyent hosting at no.de
I don't think the problem is with Socket.io

[edwardhotchkiss]

Yeah it's definitely a Heroku issue. It's probably due to paid +1 dynos vs. the free accounts.

[edwardhotchkiss]

I requested a "coupon code" but am on a queue. Did you have to wait? I don't mind paying but want to deploy with git..

Thanks James.

-edward.

[scanferla]

@ForSureRad where do I put this code?

Thanks!