vchans asked
dstala replied
vchans@discord , we suspect timeout in this case could be happening due to large dataset.
Knex.js library that we use provides default timeout set to 15000 ms (15 seconds). Could you try changing this to a higher number, say 300000.
You can find details in below video to update knex.js configuration.
https://www.youtube.com/watch?v=rS0NRwRCjx0
We need to re-configure requestTimeout parameter & set it as requestTimeout: 300000
As guided in YouTube shared above, once you open “Edit Connection JSON” under SSL & Advanced Parameters - you will find something like below
“connection”: {
“host”: “localhost”,
“port”: “3306”,
“user”: “root”,
“password”: “password”,
“database”: “sakila”
},
Change this to
“connection”: {
“host”: “localhost”,
“port”: “3306”,
“user”: “root”,
“password”: “password”,
“database”: “sakila”,
“connectTimeout”: “300000”
},
In case if issue still persists, ping here. We will look into other possible configurations required.
Apologies, my bad. Can we try with reconfiguring “requestTimeout”.
“connection”: {
“host”: “localhost”,
“port”: “3306”,
“user”: “root”,
“password”: “password”,
“database”: “sakila”,
“requestTimeout”: “300000”
},
dstala@discord , Thanks for the suggestion, now we’re getting this error in console
KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably ful
l. Are you missing a .transacting(trx) call?
I’ve added both requestTimeout and connectTimeout
o1lab replied
Try simple knexJs connection in a js file. See if it goes through. Where is database based