[JAVA-589] Don't empty connection pool on every RuntimeException Created: 21/Jun/12 Updated: 03/Apr/14 Resolved: 26/Nov/13 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | None |
| Fix Version/s: | 2.12.0, 3.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
|||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||
| Description |
|
DBTCPConnector.call/say empties the connection pool if any RuntimeException is thrown while decoding/encoding the response from/to the server. But a runtime exception does not indicate that there is anything wrong with the connections in the pool, so there is no reason to do so. |