[CSHARP-393] MongoConnectionPool should throw some kind of MongoException (MongoConnectionException?) instead of TimeoutException Created: 16/Feb/12 Updated: 11/Oct/18 Resolved: 24/May/12 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | None |
| Affects Version/s: | 1.3.1 |
| Fix Version/s: | 2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Craig Wilson |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
I propose that MongoConnectionPool should throw MongoConnectionException("Timeout waiting for a MongoConnection."). I recommend this for uniform exception handling model – user code should rely that all application-level failures (yes, I understand that the "application-level" definition is a bit vague) should be propagated with application-level exceptions – after all it's a connection error, not dissimilar to plain socket failure. |
| Comments |
| Comment by Aristarkh Zagorodnikov [ 11/Oct/18 ] |
|
Since |
| Comment by Craig Wilson [ 08/Sep/12 ] |
|
CSHAR-474 will handle this. |
| Comment by Craig Wilson [ 24/May/12 ] |
|
We will be reviewing all exceptions as part of the 2.0 release because changing things like this are backwards breaking. |