Giters

socketio / engine.io-client

The engine used in the Socket.IO JavaScript client, which manages the low-level transports such as HTTP long-polling, WebSocket and WebTransport.

Home Page:https://socket.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Uncaught Error: xhr poll error

Somebi opened this issue · comments

commented

Unhandled error, error event listener is applied on our side.
This happens time to time, due to quick server shutdown and start tests. Seems like something with polling connection establishing.

     Uncaught Error: xhr poll error
      at XHR.Transport.onError (/home/beck/optibet/src/github.com/LiflandGaming/ws-service/node_modules/engine.io-client/lib/transport.js:64:13)
      at Request.<anonymous> (/home/beck/optibet/src/github.com/LiflandGaming/ws-service/node_modules/engine.io-client/lib/transports/polling-xhr.js:128:10)
      at Request.Emitter.emit (/home/beck/optibet/src/github.com/LiflandGaming/ws-service/node_modules/component-emitter/index.js:133:20)
      at Request.onError (/home/beck/optibet/src/github.com/LiflandGaming/ws-service/node_modules/engine.io-client/lib/transports/polling-xhr.js:310:8)
      at Timeout._onTimeout (/home/beck/optibet/src/github.com/LiflandGaming/ws-service/node_modules/engine.io-client/lib/transports/polling-xhr.js:257:18)
      at ontimeout (timers.js:488:11)
      at tryOnTimeout (timers.js:323:5)
      at Timer.listOnTimeout (timers.js:283:5)
commented

Seems like closing/disconnecting client gracefully before closing the server helped in my case, but this is still a bug, not sure why Error is counted as unhandled. Don't have time to figure that out.

But the issue is that client is not handling this properly.