Closing stuck Fin_WAIT2 on application side
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- networking
Research direction
The issue identifies TCP FIN_WAIT2 and /proc/sys/net/ipv4/tcp_fin_timeout but names no repository file, test, or implementation entry point. Start by tracing how node-smpp handles socket shutdown and reviewing Node.js socket timeout behavior; define a reproducible stuck-connection case and an accepted cleanup expectation before changing anything.
Written by the indexing model from the issue text.
Description
There are some network conditions which may lead to connection being stuck in Fin_Wait2 state in defintley which is causing submit_sm to not be sent to the upstream.
$ cat /proc/sys/net/ipv4/tcp_fin_timeout
60
The kernel timeout only applies if the connection is orphaned. when the connection is still attached to a socket, the program that owns that socket is responsible for timing out the shutdown of the connection. The question is there a way to set fin_wait2 timeout on the application side to clean up the if the connection is stuck in this state for more than 60 seconds ?
- Dominant language
- JavaScript
- Stars
- 434
- Forks
- 194
- 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 farhadi/node-smpp
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
MultiprocessingOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in farhadi/node-smpp
Similar issues
-
[Bug]: Payment providers removed from config are never disabled in payment_providerPossibly taken @medusa-os-bot claimed this today. Opentype: bug
Difficulty 2/5 Half a day Newbie friendliness 82/100
medusajs/medusa#17544 · 1 comment ·
Maintainers usually reply within 1 day
-
Cookies with valid Max-Age are omitted when Expires is in the pastPossibly taken @Max-Reisinger claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sagemathinc/sagebrush#252 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Fei2411/DeepSeek-Bot#634 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days