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

Driver does not send hello over op msg protocol when serverApi is set

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      What problem are you facing?

      When serverApi is defined on a MongoClient the driver MUST send its initial message in the OpMsg format. (Relevant Spec). The Driver continues to rely on the absence of server information here that will always return false for shouldUseOpMsg.

      What driver and relevant dependency versions are you using?

      5.x

      Steps to reproduce?

      Add serverApi to a MongoClient construction, observe message sent via packet sniffing or debugging the driver.

      When fixed, likely we can unit test this with a fakeSocket of some kind to verify the opCode written to the network is 2013 (op_msg)

            Assignee:
            Unassigned Unassigned
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: