-
Notifications
You must be signed in to change notification settings - Fork 5
Request timeout issue occurring sporadically #10
Comments
The pool status object you mentioned above is not the one when the issue happened, right? Normally having request timeout is because there is no room left in the pool. So, you may increase the max option for the pool, or increase the requestTimeout. |
Thank you for your inputs. The pool status mentioned is the status when the timeout actually occurred. Therefore, I am also confused what could cause this. |
Well, I still think it might be related to the hana connection during that period of time. If conn.connect failed, the createPoolResource (Operator.js) will be failed as well and the related resource will be removed from the pool. Please have a check with the indexserver trace, whether you can see the error/warning/info that relates to the connection issue. As you mentioned, this issue is sporadically occurring, please enable the trexnet info trace and sqlsession debug trace. To avoid the traces get overwritten, you can increase the trace size and trace number via: to restore it: Please let me know if you can reproduce this on your test system, then we may enable the debug trace for the pool. Regards, |
I've used the However, eventually I have dismissed the pool completely in favour of the native pooling mechanism of the |
During execution of method getConnection() on pool object, we receive the below error
"Request timeout. Request info: (id: 54, creation time: 1599638811640)","type":"log","custom_fields":{"stack":"Error: Request timeout. Request info: (id: 54, creation time: 1599638811640)\n at Request._fireTimeout (/home/vcap/app/node_modules/hdb-pool/lib/Request.js:114:17)\n at Timeout. (/home/vcap/app/node_modules/hdb-pool/lib/Request.js:92:43)\n at listOnTimeout (internal/timers.js:549:17)\n at processTimers (internal/timers.js:492:7)"}}
As this is sporadically occurring, I am not quite sure what causes this issue. The only way to resolve this as of now is to re-start the application.
Pool status object
"pool":"{"size":0,"min":2,"max":10,"available":0,"timeout":0}","request":"{"number":1,"pending":0,"max":0,"resolved":53,"rejected":0,"timeout":2}"}
Could you please help me understand how can we resolve this? This is causing downtime for our application.
Thanks!
The text was updated successfully, but these errors were encountered: