Resources are not cleaned properly for call procedures
Closed this issue · 0 comments
niveathika commented
Description:
Connection unavailable after couple of call procedure failures. From the behaviour we see that active connections are not released back to the pool after a call failure. This is a new behaviour specifically for the redshift.driver only as we did not observe this behaviour in others.
As a fix we can forcefully close the connection from our side if the results returned is an error.