RequestError: Timeout: Request failed to complete in 15000ms #11035

nash90 · 2019-06-05T04:11:00Z

Issue: unable to set requestTimeout with configuration parameter for "mssql" dilect
No matter whatever value is in requestTimeout parameter, the driver sets default value of "15000ms".
Hence, Timeout error occurs for all query that takes longer than 15s.

Application log is as follows:

Executing (default): SELECT [AnalysisTagID], [RefDate], [CategorySet], [AssetID], [Category] FROM [EMA_RiskAllocCategoriesView] AS [EMA_RiskAllocCategoriesView] ORDER BY [EMA_RiskAllocCategoriesView].[AssetID] OFFSET 0 ROWS FETCH NEXT 3 ROWS ONLY;
Error EMA_RiskAllocCategoriesView.getAll DatabaseError [SequelizeDatabaseError]: Timeout: Request failed to complete in 15000ms
    at Query.formatError (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/sequelize/lib/dialects/mssql/query.js:309:12)
    at Request.userCallback (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/sequelize/lib/dialects/mssql/query.js:69:23)
    at Request.callback (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/request.js:37:27)
    at Connection.message (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:2181:24)
    at Connection.dispatchEvent (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1172:36)
    at MessageIO.<anonymous> (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1045:14)
    at MessageIO.emit (events.js:200:13)
    at Message.<anonymous> (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/message-io.js:32:14)
    at Message.emit (events.js:205:15)
    at endReadableNT (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/node_modules/readable-stream/lib/_stream_readable.js:1077:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) {
  name: 'SequelizeDatabaseError',
  parent: RequestError: Timeout: Request failed to complete in 15000ms
      at RequestError (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/errors.js:32:12)
      at Connection.requestTimeout (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1117:21)
      at Timeout._onTimeout (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1085:14)
      at listOnTimeout (internal/timers.js:531:17)
      at processTimers (internal/timers.js:475:7) {
    message: 'Timeout: Request failed to complete in 15000ms',
    code: 'ETIMEOUT',
    sql: 'SELECT [AnalysisTagID], [RefDate], [CategorySet], ' +
      '[AssetID], [Category] FROM [EMA_RiskAllocCategoriesView] ' +
      'AS [EMA_RiskAllocCategoriesView] ORDER BY ' +
      '[EMA_RiskAllocCategoriesView].[AssetID] OFFSET 0 ROWS ' +
      'FETCH NEXT 3 ROWS ONLY;'
  },

What are you doing?

sequelize is instantiated as follows where requestTimeout is set to 30s

const sequelize = new Sequelize(config.db.schema, config.db.username, config.db.password, {  
  "host": config.db.url,
  "dialect": "mssql",
  "dialectOptions": {
    "requestTimeout": 300000
  },
  pool: {
    max: 5,
    min: 0,
    acquire: 30000,
    idle: 10000
  }
});

A query that does full scan in a large table is run as follows:

EMA_RiskAllocCategoriesView.findAll({
    }).catch((err)=>{
      console.log("Error EMA_RiskAllocCategoriesView.getAll",err)
    });

To Reproduce
Steps to reproduce the behavior:

Initiate sequelize with requestTimeout set to 30s
Use a query that takes longer than 15s
See error which says "Request failed to complete in 15000ms"

What do you expect to happen?

Not thow request timeout error for queries that run for 30s if sequelize is set to have requestTimeout of 30s.

What is actually happening?

Timeout Error for all query that takes longer than 15 s

Output, either JSON or SQL

Executing (default): SELECT [AnalysisTagID], [RefDate], [CategorySet], [AssetID], [Category] FROM [EMA_RiskAllocCategoriesView] AS [EMA_RiskAllocCategoriesView] ORDER BY [EMA_RiskAllocCategoriesView].[AssetID] OFFSET 0 ROWS FETCH NEXT 3 ROWS ONLY;
Error EMA_RiskAllocCategoriesView.getAll DatabaseError [SequelizeDatabaseError]: Timeout: Request failed to complete in 15000ms
    at Query.formatError (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/sequelize/lib/dialects/mssql/query.js:309:12)
    at Request.userCallback (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/sequelize/lib/dialects/mssql/query.js:69:23)
    at Request.callback (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/request.js:37:27)
    at Connection.message (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:2181:24)
    at Connection.dispatchEvent (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1172:36)
    at MessageIO.<anonymous> (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1045:14)
    at MessageIO.emit (events.js:200:13)
    at Message.<anonymous> (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/message-io.js:32:14)
    at Message.emit (events.js:205:15)
    at endReadableNT (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/node_modules/readable-stream/lib/_stream_readable.js:1077:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) {
  name: 'SequelizeDatabaseError',
  parent: RequestError: Timeout: Request failed to complete in 15000ms
      at RequestError (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/errors.js:32:12)
      at Connection.requestTimeout (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1117:21)
      at Timeout._onTimeout (/Users/abinash/Desktop/my-app/new-dashboard/ember-electron/resources/sapiat-server/node_modules/tedious/lib/connection.js:1085:14)
      at listOnTimeout (internal/timers.js:531:17)
      at processTimers (internal/timers.js:475:7) {
    message: 'Timeout: Request failed to complete in 15000ms',
    code: 'ETIMEOUT',
    sql: 'SELECT [AnalysisTagID], [RefDate], [CategorySet], ' +
      '[AssetID], [Category] FROM [EMA_RiskAllocCategoriesView] ' +
      'AS [EMA_RiskAllocCategoriesView] ORDER BY ' +
      '[EMA_RiskAllocCategoriesView].[AssetID] OFFSET 0 ROWS ' +
      'FETCH NEXT 3 ROWS ONLY;'
  },

Environment

Dialect:

mssql

Dialect library version: tedious 6.1.2
Database version: mcr.microsoft.com/mssql/server:2017-latest (docker)
Sequelize version: 5.8.7
Node Version: v12.3.1
OS: osx
If TypeScript related: TypeScript version: XXX
Tested with latest release:

No

Self investigation.
hard coded fix is to change the value of the following variable in "lib/connection.js" module of tedious library
const DEFAULT_CLIENT_REQUEST_TIMEOUT = 15 * 1000;

The text was updated successfully, but these errors were encountered:

cbogwill · 2019-07-02T19:32:35Z

@nash90:
I had the same issue. Try doing this instead:

"dialectOptions": {
    options: { "requestTimeout": 300000 }
  },

papb · 2019-07-25T00:52:21Z

@nash90 Does the above workaround work for you?

Yaowenjie · 2019-08-01T02:25:39Z

@cbogwill
It seems not working for my case. BTW, I am using mssql dialect as well.

nash90 · 2019-08-01T04:58:50Z

@papb @Yaowenjie
The solution provided by @cbogwill worked.

nash90 · 2019-08-01T04:59:41Z

@nash90:
I had the same issue. Try doing this instead:
"dialectOptions": {
    options: { "requestTimeout": 300000 }
  },

Thanks, This solution worked for mssql.

Yaowenjie · 2019-08-01T05:02:55Z

@cbogwill @nash90
Yes, that works. I missed the options level. Thank you, all!

nash90 · 2019-08-01T05:09:43Z

@cbogwill @nash90
Yes, that works. I missed the options level. Thank you, all!

By the way, that setting was in sequelize source code "lib/dialects/mssql/connection-manager.js"
https://github.com/sequelize/sequelize/pull/11045/files#diff-3aa0e1a84e1c794951afaa682fde719dR60

ongkristopher · 2020-01-10T03:58:34Z

@nash90:
I had the same issue. Try doing this instead:
"dialectOptions": {
    options: { "requestTimeout": 300000 }
  },

Ignoring invalid configuration option passed to Connection: options. This is currently a warning, but in future versions of MySQL2, an error will be thrown if you pass an invalid configuration options to a Connection

this is showing on my log using that format.

jeserg · 2020-02-07T08:08:01Z

I am using the mssql driver and my configuration -
const config = {
user: 'login',
password: 'pass',
server: '10.11.24.15',
port: 1433,
database: 'base',
options: {
'enableArithAbort': true,
'requestTimeout': 130000,
'idleTimeoutMillis': 130000
},
pool: {
max: 10,
min: 0,
idleTimeoutMillis: 130000
}
}

ashokkumarg · 2020-05-21T07:43:16Z

I tried using both of the dialectOptions to the configuration as below but still I face the same issue

dialectOptions: {
"requestTimeout": 300000
}

dialectOptions: {
options: { "requestTimeout": 300000 }
}

const DBConfig = {
  user: 'username',
  password: '*******',
  host: 'host name',
  port: 1455,
  database: 'database name',
  server: 'server name',
  dialect: "mssql"
};

**RequestError: Timeout: Request failed to complete in 15000ms**

854770857 · 2020-11-11T08:31:58Z

@ashokkumarg
How was it resolved in the end?

jepalen · 2020-12-28T12:23:53Z

For me in NodeJs with Mssql worked just this small change:
just put outside of the options the field requestTimeout

const config = {
user: 'login',
password: 'pass',
server: '10.11.24.15',
port: 1433,
database: 'base',
'requestTimeout': 130000,
options: {
'enableArithAbort': true,
'idleTimeoutMillis': 130000
},

davidbouckaert · 2021-06-02T07:24:09Z

Hello, anno 2021 I've got this working with the following code (I'm connecting to Azure, so I need encryption).

  client: 'mssql',
  connection: {
    host: '*****',
    user: '*****',
    password: '*****',
    options: { requestTimeout: 300000, encrypt: true },
  },
});

tensajougan8 · 2021-10-09T11:52:36Z

You need to hard code it
add this to the config

dialectOptions:{
requestTimeout: 300000
}

add the following to
\sequelize\lib\dialects\mssql\connection-manager-> connectionConfig

requestTimeout: config.dialectOptions.requestTimeout

by @nash90

github-actions · 2021-11-09T00:09:01Z

This issue has been automatically marked as stale because it has been open for 14 days without activity. It will be closed if no further activity occurs within the next 14 days. If this is still an issue, just leave a comment or remove the "stale" label. 🙂

SpringsTea · 2022-04-20T18:59:35Z

A lot of different methods thrown around here, so I figured I'd put out what actually worked for me.

const connection = require('knex')({
  client: 'mssql',
  connection: {
    host :  'hostaddress',
    user : user,
    password : password,
    requestTimeout: 600000,// this part worked for me, 10 min timeout
    database : 'DBName'
  }
});

Putting requestTimeout in options or dialectOptions was not working for me.

jamessandoval mentioned this issue Jun 6, 2019

fix(options): add 'requestTimeout' to dialect:mssql #11045

Closed

papb added status: awaiting response For issues and PRs. OP must respond (or change something, if it is a PR). Maintainers have no action type: other For issues and PRs. Something that does not fit in any of the other "type:" labels. labels Jul 25, 2019

papb added the existing workaround For issues. There is a known workaround for this issue. label Aug 1, 2019

papb self-assigned this Aug 1, 2019

papb added status: understood For issues. Applied when the issue is understood / reproducible. and removed status: awaiting response For issues and PRs. OP must respond (or change something, if it is a PR). Maintainers have no action labels Aug 1, 2019

github-actions bot added the stale label Nov 9, 2021

WikiRik removed the stale label Nov 15, 2021

WikiRik unassigned papb Oct 23, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RequestError: Timeout: Request failed to complete in 15000ms #11035

RequestError: Timeout: Request failed to complete in 15000ms #11035

nash90 commented Jun 5, 2019 •

edited

cbogwill commented Jul 2, 2019

papb commented Jul 25, 2019

Yaowenjie commented Aug 1, 2019 •

edited

nash90 commented Aug 1, 2019

nash90 commented Aug 1, 2019 •

edited

Yaowenjie commented Aug 1, 2019 •

edited

nash90 commented Aug 1, 2019 •

edited

ongkristopher commented Jan 10, 2020

jeserg commented Feb 7, 2020 •

edited

ashokkumarg commented May 21, 2020 •

edited

854770857 commented Nov 11, 2020

jepalen commented Dec 28, 2020

davidbouckaert commented Jun 2, 2021 •

edited

tensajougan8 commented Oct 9, 2021

github-actions bot commented Nov 9, 2021

SpringsTea commented Apr 20, 2022

RequestError: Timeout: Request failed to complete in 15000ms #11035

RequestError: Timeout: Request failed to complete in 15000ms #11035

Comments

nash90 commented Jun 5, 2019 • edited

What are you doing?

What do you expect to happen?

What is actually happening?

Environment

cbogwill commented Jul 2, 2019

papb commented Jul 25, 2019

Yaowenjie commented Aug 1, 2019 • edited

nash90 commented Aug 1, 2019

nash90 commented Aug 1, 2019 • edited

Yaowenjie commented Aug 1, 2019 • edited

nash90 commented Aug 1, 2019 • edited

ongkristopher commented Jan 10, 2020

jeserg commented Feb 7, 2020 • edited

ashokkumarg commented May 21, 2020 • edited

854770857 commented Nov 11, 2020

jepalen commented Dec 28, 2020

davidbouckaert commented Jun 2, 2021 • edited

tensajougan8 commented Oct 9, 2021

github-actions bot commented Nov 9, 2021

SpringsTea commented Apr 20, 2022

nash90 commented Jun 5, 2019 •

edited

Yaowenjie commented Aug 1, 2019 •

edited

nash90 commented Aug 1, 2019 •

edited

Yaowenjie commented Aug 1, 2019 •

edited

nash90 commented Aug 1, 2019 •

edited

jeserg commented Feb 7, 2020 •

edited

ashokkumarg commented May 21, 2020 •

edited

davidbouckaert commented Jun 2, 2021 •

edited