-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outparams is null when using connection pool and previously DB error in the connection #952
Comments
We have also faced the same issue. Any errors in executing sp corrupts the connection in the pool. The connection.close() doesn’t really restore the connection to a clean stats. Out params can never be fetched post a single error. |
@girish-jha I am trying to reproduce the problem. Meanwhile if you can share a complete test program to reproduce the problem, it would really help me to make progress. Thanks. |
@girish-jha For both success and error case, just before |
Hi @bimalkjha, i have created a PR that resolves this issue for us. Could you please review |
* update precompiled binaries (Bimal Jha) * fea: add support for pool.initAsync() API, PR #953, issue #952 (Bimal Jha) * fix: compilation issue on z/OS, define SQL_BOOLEAN, issue #961 (Bimal Jha) * build(deps): bump axios from 1.5.0 to 1.6.0 (#964) (dependabot[bot]) * fix promise bug of executeNonQuery api, issue #960 (Bimal Jha) * read Db2 credential from Env var for testing (Bimal Jha)
ibm_db@3.2.3 should fix this issue. thanks. |
Hi Team,
I am using node ibm_db version 3.2.2. I am using the connection pool and suppose a database error occurred in one of the connections of the pool. In such a case in all the other successful queries we are getting outparams as null in that connection(where error had occurred previously.
this is how i am creating the connection pool:
This is how i am calling execute
The text was updated successfully, but these errors were encountered: