In node v18 and above, server is getting closed quickly without honoring the keep-alive timeouts #52224
Replies: 4 comments 1 reply
-
any insights here @bnoordhuis ? Something you came across. I read few threads where it talks about race condition. But in my Unit test, i don't expect that to happen. Also, keepalive timeout is 20 secs which is more than enough time.
![]() |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
After digging more, I found that this behavior started in node v18.19.0 . It worked fine until v18.18.2 |
Beta Was this translation helpful? Give feedback.
-
fixed in #52336 |
Beta Was this translation helpful? Give feedback.
-
In my unit tests, I am seeing a behavior in node v18 and above that, Server is getting closed quickly after calling server.close() without honoring the keep-alive timeouts. Hence, new request is failing. Expectation: New request shouldn't fail as it should use the existing open connection unless closed explicitly.
It works fine with Node v16.
Only difference in code while running node v16 and node 18 - I have
@SECLEVEL=0
in ciphers for node 18. Not sure if it's related.I will try to get a sample code to reproduce. Just wanted to check if anyone came across this
Beta Was this translation helpful? Give feedback.
All reactions