Issue Details (XML | Word | Printable)

Key: DNET-818
Type: Task Task
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jiri Cincura
Reporter: Jiri Cincura
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
.NET Data provider

Connections that are "broken" should not go back to the pool #breaking

Created: 14/May/18 11:52 AM   Updated: 06/Jun/18 11:48 AM
Component/s: ADO.NET Provider
Affects Version/s: None
Fix Version/s: 6.0.0.0

Issue Links:
Replace
 


 Description  « Hide
* 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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.