any workaround on multiple socket.io connection after reconnect

[Vedratna Velani]

Hi guys,

I know this is known issue right now: https://github.com/LearnBoost/socket.io/issues/430

But I want to know if anybody knows any workaround to get rid of multiple connection after this as I want to avoid multiple update with this.

At client side will socket.disconnect() removes all the connections? will following code works to remove multiple connection after reconnect?

socket = io.connect(url)
socket.on('connect', function(){
if(multipleConnect) {
socket.disconnect();
socket.removeAllListeners('connect');
io.sockets = {};
socket = io.connect(url);
socket.on('connect', functionToConnect);
}
})

I am not able to test this locally as not able to reproduce it locally.

Thanks,
Ved

[ankur]

I had a similar problem affecting my code
what i did was add the listener methods outside of 'connect' function,
now i get only one event fired

instead of this

socket = io.connect(url)
socket.on('connect', function(){

socket.on('message', function (msg) {
});
});

now i do

socket = io.connect(url)
socket.on('connect', function(){

});

socket.on('message', function (msg) {
});

it appears work right..
hope this helps

[ankur]

i had the same problem , was getting multiple events on receiving
data.
instead of this

socket = io.connect(url);
socket.on('connect', function () {

socket.on('message', function (msg) {
});
});

i did this,

socket = io.connect(url);
socket.on('connect', function () {

});
socket.on('message', function (msg) {
});

this seems to work all right and multiple events don't seem to fire.
i think it is because previous registered listener doesn't gets
unregistered after a successful re-connection attempt

[Vedratna Velani]

I am already having the second implementation and it doesn't seem to work for me, to me it looks like multiple connections gets generated on same 'socket' reference, because I have 'socket = io.connect(url) only once in my code, where socket gets assigned and like your second implementation I am adding evenlisteners to same socket independently, not inside the 'connect'. So it can't be get reassigned automatically on reconnection.

Thanks,
Ved

[ankur]

which version of socket.io do you use .. ?

[Vedratna Velani]

0.8.7 the latest one.

Thanks,
Ved

[ankur]

Is your server under heavy load....!!

[Vedratna Velani]

yes. sometime.

Thanks,
Ved

[ankur]

i think the issue is solved in jsonp transport . try that and
see......!!

[Vedratna Velani]

overall issue is not fixed yet. And I want to use websocket where issue is still there. It is regarding opening multiple transport at the same time. I think it has been fixed by 3rd-Eden in his branch where he fixed the multiple reconnection issue. He already did pull request, so fix might come with next socket.io release. Till that as a workaround I choose to disable reconnection on socket-io-client, I am handling it outside.

Thanks,
Ved

[Vedratna Velani]

To disable reconnection on socket.io-client, I made a small fix here:
https://github.com/LearnBoost/socket.io-client/pull/346

Thanks,
Ved

[Sergii Boiko]

I've did a fix, but it works only for JSONP-kind of handshake.

https://github.com/LearnBoost/socket.io-client/pull/342

You can disable appropriate condition and prevents AJAX-handshake. So it will work for anybody.