You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request timeouts mean requests time out and connections on which the request timeout happened are added back to the connection pool, ready to be used again in the future
Current Behavior
Request timeout settings are being ignored
These are my 4 files containing the test code. A few strings you'll have to substitute before running:
my CPU usage spikes like crazy after connection.execSql(sqlRequest) is called.... :/
I've been playing around with some of the timeout settings and I think they are just being ignored. For example, request timeout is set to 5000 millis, it does not timeout after 5 seconds, it just keep going... connection is not being released back to the pool... am I doing something wrong? Maybe there is some config on the SQL server I need to check?
Expected Behavior
Request timeouts mean requests time out and connections on which the request timeout happened are added back to the connection pool, ready to be used again in the future
Current Behavior
Request timeout settings are being ignored
These are my 4 files containing the test code. A few strings you'll have to substitute before running:
<YOUR_SLOW_SQL_STATEMENT_HERE>
<YOUR_DB_USER_NAME_HERE>
<YOUR_DB_USER_PASSWORD_HERE>
<YOUR_SERVER_IP_HERE>
<YOUR_DB_PORT_HERE>
'<YOUR_DB_NAME_HERE>'
then run by invoking 'node app.js'
my CPU usage spikes like crazy after connection.execSql(sqlRequest) is called.... :/
I've been playing around with some of the timeout settings and I think they are just being ignored. For example, request timeout is set to 5000 millis, it does not timeout after 5 seconds, it just keep going... connection is not being released back to the pool... am I doing something wrong? Maybe there is some config on the SQL server I need to check?
Steps to Reproduce (for bugs)
package.json
app.js
sqlrunner.js
sqlserverConnectionPool.js
Reason For Request (for feature requests)
Possible Solution
Background Details
Environment
The text was updated successfully, but these errors were encountered: