Query Timeouts

[katsutori]

Hello,

Trying to set an explicit query timeout. Looking at the documentation, I should be able to use conn.setAttrSync, but I get conn.setAttrSync is not a function returned. Is this no longer a valid method, exclusive to certain versions, or something else?

[bimalkjha]

@katsutori conn.setAttrSync() is supported API and not removed. Probably, the way your code is calling it, might have issue. Good to share your test program with output to understand issue.
Also, you can see use of this API is test program: https://github.com/ibmdb/node-ibm_db/blob/master/test/test-attributes.js
You can run this test program by updating connection info in ibm_db/test/config.json file. Thanks.

[katsutori]

Yes, I have the query timeout working with the interrupt set to 2. What I am seeing now is pool saturation. Looks like in a high traffic api where a lot of timeouts are happening, the pool cleanup doesn't happen fast enough and jams up the pool. Any resolution to better handling of the pool?

[bimalkjha]

@katsutori Pool cleanup happens for idle connection which are not in use for idleTimeout seconds(default 30min) passed to Pool(). Also, autoCleanIdle should be set to true. Then only, during conn.close()/conn.closeSync(), pool cleanup function gets called.

I think you might have set setMaxPoolSize to some lower value as pool can not have more than setMaxPoolSize connections if it is set and any new connection request will wait for some connection getting closed. Increase setMaxPoolSize value if you are using it or do not set it.
Also, if pool.init() is called with sufficient number, any new connection request for more than init count will be slower as it need to establish new connection and move to pool.
Good to share your test program, so that I can understand your logic and share any suggestion. Thanks.

[bimalkjha]

@katsutori Please share the operating system name and db2level output of clidriver too. Thanks.