SockJS is not emitting 'close' event
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, nodejs
- Domain
- backend, networking
Research direction
The issue does not identify a file, test, or entry point. Start by investigating SockJS close-event handling and comparing tracked sockets with active users in the production deployment, where the problem occurs. Done means identifying why stale sockets remain and verifying a fix with a regression test or reproducible production case.
Written by the indexing model from the issue text.
Description
I have a chat (facebook style chat) than during the day it gets over 3000 open sockets (online users).
But during the night, I have a maximum of 400 users online, yet the chat (with sockjs) accuses that it still has, more or less, 2000 open sockets.
If I restart the server (browser will automatically reconnect) than my chat server back to having only 400 sockets (which proves that 2000 connections were incorrect).
In developing this bug does not exist, only in production ...
What can I do to find out what's going on?
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 305
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from sockjs/sockjs-node
-
CVE issues (uuid)Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sockjs/sockjs-node#329 ·
-
Please bump uuid to version ^14Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sockjs/sockjs-node#316 · 14 comments · 26 reactions ·
-
Is prefix a must?Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
sockjs/sockjs-node#311 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
sockjs/sockjs-node#304 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
sockjs/sockjs-node#301 ·
All issues in sockjs/sockjs-node
Similar issues
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jaegertracing/jaeger-ui#4596 ·
Maintainers usually reply within 1 day
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days