MongoConnectionPool should throw some kind of MongoException (MongoConnectionException?) instead of TimeoutException

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • 2.0
    • Affects Version/s: 1.3.1
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Craig Wilson
            Reporter:
            Aristarkh Zagorodnikov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: