Closed SteadEXE closed 1 year ago
If you turn the debug logs on (set the DEBUG
env var) what output do you get? Do you see the logs stop when the event loop is blocked?
Do you have other code that makes up your application that could be contributing to the event loop blocking issue?
Sorry for the delay, I didn't had the issue for a while, next time it happens, I will try 👍
OK - if you're not experiencing it at the moment, I'll close this and will re-open if you're able to give an update.
Sometime, randomly queries start to fail, while it continues to work using the same user and same query on SQL Server Management Studio. I don't know yet if this is caused by the node-mssql/tedious or an issue with SQL server itself. It was looking like this issue: https://github.com/tediousjs/node-mssql/issues/1407 What is weird, is that when a request timeout. CPU usage rises up to 100% on one core. And the whole node process stop to react to CTRL+C or incoming HTTP requests. Aslong the requests work back, CPU usage fall to a normal CPU usage.
Feel free to ask me any details. We are really struggling troubleshooting the cause of the issue. As mentioned, for the queries failing we are still not sure why it randomly fails.
Expected behaviour:
I expect my requests to not fail (if it's a bug within tedious ofcourse). I also expect the event loop to not be blocked.
Actual behaviour:
This is one of the failing query which continues to work in SQL Studio :
Here is the logs:
Configuration:
Software versions