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

Connections that are "broken" should not go back to the pool [DNET818] #753

Closed
firebird-automations opened this issue May 14, 2018 · 4 comments

Comments

@firebird-automations
Copy link

Submitted by: @cincuranet

Replaces DNET668

* If there was a problem in communication, aka "broken" connection, do not return the connection back to the pool.
* The fact that connection is broken is know only if some operation was performed (aka broken connections can be in the pool until these are used).

Retry logic is up to the developer, because in the library can't understand what the transaction is possibly doing, hence whether retry is possible.

Commits: 4abfc74

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Fix Version: 6.0.0.0 [ 10850 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue replaces DNET668 [ DNET668 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

summary: Connections that are "broken" should not go back to the pool => Connections that are "broken" should not go back to the pool #⁠breaking

@cincuranet cincuranet changed the title Connections that are "broken" should not go back to the pool #breaking [DNET818] Connections that are "broken" should not go back to the pool [DNET818] May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants