Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-3949

Investigate MongoClient.connect behavior with large minPoolsize on Windows

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:

      What problem are you facing?

      This is a follow up to NODE-3928 .  

      A user reported that when using a minPoolSize of 50 or 100 (potentially any non-zero minPoolSize) on Windows, if they attempt to connect to an empty port, the driver throws an error that crashes the process.  This only occurs on Windows.  We have identified the reason our driver is crashing the user's process and the fix will be tracked in NODE-3918.

      The error that is crashing the user's process is being thrown when we attempt to parse a response from the server.  This is odd, because the user is connecting to an empty port so no data should be sent back. 

      Our two theories to explain this behavior are either that we're somehow re-using a buffer somewhere and decoding data that is invalid or that the port was somehow not empty.


      Acceptance Criteria

      • Determine why the driver attempts to parse data when we attempt to connect to an empty port on Windows with a large minPoolSize.

            Unassigned Unassigned
            bailey.pearson@mongodb.com Bailey Pearson
            0 Vote for this issue
            1 Start watching this issue