socket.io: socket.io-client 4.8.0 automatic reconnect is not working
Describe the bug I have a client which connects to server If the server stops and restarts the connect event is not called anymore
In version 4.7.5 the connect event was called when the server restarts and opens the websocket
Socket.IO client version: 4.8.0
Expected behavior The connect event should be called automatically if the server restarts and opens the websocket
Platform: NodeJs 16 on Ubuntu 20.04 and also in Chromium 128.0.6613.119
Additional context On 4.7.5 I get multiple times this connect_error event until it reconnects.
TransportError: xhr poll error
at Polling.onError (/home/sruetzler/data/workspace/gitlab/target/installer/rauc-api-client/node_modules/engine.io-client/build/cjs/transport.js:47:37)
at Request.<anonymous> (/home/sruetzler/data/workspace/gitlab/target/installer/rauc-api-client/node_modules/engine.io-client/build/cjs/transports/polling.js:238:18)
at Request.Emitter.emit (/home/sruetzler/data/workspace/gitlab/target/installer/rauc-api-client/node_modules/@socket.io/component-emitter/lib/cjs/index.js:143:20)
at Request.onError (/home/sruetzler/data/workspace/gitlab/target/installer/rauc-api-client/node_modules/engine.io-client/build/cjs/transports/polling.js:343:14)
at Timeout._onTimeout (/home/sruetzler/data/workspace/gitlab/target/installer/rauc-api-client/node_modules/engine.io-client/build/cjs/transports/polling.js:316:30)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7) {
description: 0,
context: XMLHttpRequest {
UNSENT: 0,
OPENED: 1,
HEADERS_RECEIVED: 2,
LOADING: 3,
DONE: 4,
readyState: 4,
onreadystatechange: [Function (anonymous)],
responseText: 'Error: connect ECONNREFUSED 192.168.70.132:443\n' +
' at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)',
responseXML: '',
status: 0,
statusText: Error: connect ECONNREFUSED 192.168.70.132:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '192.168.70.132',
port: 443
},
open: [Function (anonymous)],
setDisableHeaderCheck: [Function (anonymous)],
setRequestHeader: [Function (anonymous)],
getResponseHeader: [Function (anonymous)],
getAllResponseHeaders: [Function (anonymous)],
getRequestHeader: [Function (anonymous)],
send: [Function (anonymous)],
handleError: [Function (anonymous)],
abort: [Function (anonymous)],
addEventListener: [Function (anonymous)],
removeEventListener: [Function (anonymous)],
dispatchEvent: [Function (anonymous)]
},
type: 'TransportError'
}
on 4.8.0 I get this errror once and after that I get this endless
No transports available
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 5
- Comments: 17 (3 by maintainers)
Commits related to this issue
- use custom reconnect logic for socketio instead of what is built in, due to https://github.com/socketio/socket.io/issues/5197 — committed to sagemathinc/cocalc by williamstein a year ago
We based the conclusion that the socket should try to automatically reconnect since we had this listener function on the
connect_errorevent. And even though it logged the error as transient, a reconnect attempt was never initialized.None of the below listener function were ever triggered when the backend was killed and the above mentioned transient connection error log was triggered:
@FredrikAugust as I said earlier, I wasn’t able to reproduce at all… It looks like an environment-specific issue, otherwise I think that we would have a lot more user reports.
No, still can’t upgrade past 4.7.5
Not that I know of @joweste. We ended up writing our own logic…
Hey @darrachequesne
Here’s how our frontend connects
I am also facing this issue. It’s pretty major since our “online users” counter just drops to 0 anytime we push updates to our code base. I think going back to 4.7.5 is the move for now
We’re also seeing that it doesn’t automatically reconnect when the transport is broken using websockets.