MongoConnection.Close() should always call TcpClient.Close()

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 1.11
    • Component/s: Connectivity
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      TcpClient creates a socket when the TcpClient is first constructed but doesn't open it right away.

      So it might be possible for a disconnected TcpClient to hold on to an ephemeral port even though it's not connected.

      Because of this, MongoConnection.Close() should always call TcpClient.Close().

            Assignee:
            Robert Stam
            Reporter:
            Andrew Young (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: