Skip to content
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

Resources are not cleaned properly for call procedures #6626

Closed
niveathika opened this issue Jun 12, 2024 · 0 comments · Fixed by ballerina-platform/module-ballerina-sql#715
Assignees
Labels
module/sql Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug

Comments

@niveathika
Copy link
Contributor

niveathika commented Jun 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/sql Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant