SocketCluster / SocketCluster/socketcluster-server
Pong Timeout
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 109
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm using socketcluster-server with @redux-devtools/cli and I get ping/pong timeouts even with default settings.
Version that is used is 17.x
I an se that inner ping messages are sent correctly but they are not received from time to time in message handler therefore this code is executed and connection is reset:
this._pingTimeoutTicker = setTimeout(() => {
console.log("PING TIMEOUT")
this._destroy(4001);
this.socket.close(4001);
}, this.server.pingTimeout);
What could be the reason?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the ping/pong handling around the shown _pingTimeoutTicker callback and reproduce the intermittent timeout with socketcluster-server 17.x and @redux-devtools/cli using default settings. Check where ping messages enter the message handler and compare the timeout path with the connection lifecycle. Done means the cause is identified and the issue has a verified fix or a clearly documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100