Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Configuring SQL Server timeout

See original GitHub issue

Environment

Knex version: 0.19.5 Database + version: SQL Server 2018 OS: Windows (AWS RDS)

@smorey2.

Bug

This may not strictly be a bug and more of a bug/feature request hybrid (I’d lean towards the former). When setting the connectionTimeout option for SQL Server, it doesn’t seem to actually apply - i.e., the default is 15000ms, and after setting the value to 30000, it still times out at 15000. Is changing the request timeout possible with SQL Server?

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

juicetincommented, Feb 19, 2020

Hi @elhigu

    client: "mssql",
    connection: {
      host: STG_HOST,
      user: STG_USER,
      password: STG_PASSWORD,
      port: Number(STG_PORT),
      database: STG_DB,
      connectionTimeout: 20000,
    }

This is where the connectionTimeout option was set, as you pointed out in a past issue https://github.com/knex/knex/issues/2699

However, this option didn’t take effect, as the default timeout of 15000ms was still being enforced (as stated in the error when knex killed the request at 15000ms).

0reactions

woodchuckcommented, Nov 17, 2021

For the benefit of future travelers, I believe this should be specified as follows. Note connectTimeout vs. connectionTimeout.

client: "mssql",
connection: {
  host: STG_HOST,
  user: STG_USER,
  password: STG_PASSWORD,
  port: Number(STG_PORT),
  database: STG_DB,
  options: {
    connectTimeout: 20000,
  }
}

https://github.com/tediousjs/tedious/issues/778 https://tediousjs.github.io/tedious/api-connection.html#function_newConnection