Initial connection handshake does not publish heartbeat

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Unknown
    • 1.12.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Fully Compatible
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      When a connection is made, the following order is expected:

      • Create Monitor
      • run handshake ("ismaster" with client metadata, without maxAwaitTimeMS)
      • get handshake response
      • publish HeartbeatSucceededEvent

      GODRIVER-2577 introduced a bug that prevents the block that is responsible for publishing a heartbeat succeeded event, using the “isNilConn” variable which is not reset from the original declaration.
       

            Assignee:
            Preston Vasquez
            Reporter:
            Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: