This work item is about the part of [1114 "Connection resiliency: possible data corruption if connection fails after transaction commit"](https://entityframework.codeplex.com/workitem/1114) we are prioritizing for EF6. As part of it we should:
1. Gather some more information about the incidence of this problem, e.g. how often a successful transaction commit on the server could end up on a client-side exception?
2. How does the problem manifest? Is there a specific kind of exception or error code you would observe on the client, e.g. a time out?
3. Implement the necessary changes based on information gathered. Changes could consist on:
* Removing specific errors from the retryable list
* Stop retrying if the exception comes form a transaction commit
* Some form of hybrid of the options above
1. Gather some more information about the incidence of this problem, e.g. how often a successful transaction commit on the server could end up on a client-side exception?
2. How does the problem manifest? Is there a specific kind of exception or error code you would observe on the client, e.g. a time out?
3. Implement the necessary changes based on information gathered. Changes could consist on:
* Removing specific errors from the retryable list
* Stop retrying if the exception comes form a transaction commit
* Some form of hybrid of the options above