You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 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.
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
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
The text was updated successfully, but these errors were encountered: