Closed girish-jha closed 7 months ago
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 connection.closeSync()
, add statement.closeSync()
too and verify. Let me know if you see any difference. Thanks.
Hi @bimalkjha, i have created a PR that resolves this issue for us. Could you please review
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