Exceptions raised during address resolution are not mapped to Mongo::Error

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.13.0.beta1, 2.12.2
    • Affects Version/s: None
    • Component/s: Connections
    • None
    • None
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None

      If address resolution fails (when creating a connection), the produced exception is not mapped to a Mongo::Error subclass, ends up being unhandled, and causes the connection pool populator thread to exit.

              Assignee:
              Oleg Pudeyev (Inactive)
              Reporter:
              Oleg Pudeyev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: