Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20624

NetworkInterfaceASIO does not always initialize messageId and responseTo

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • Fully Compatible
    • ALL
    • Platform A (10/09/15)
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      found with valgrinding the stress test.

      we initialize the messageId in messageFromRequest(), but in some cases we manually create a message (e.g. the LegacyRequest used for sending isMasters) and do not go through messageFromRequest(). In that case the messageId will be uninitialized. Also, responseTo() was always uninitialized. We should initialize it to 0.

            Assignee:
            adam.midvidy Adam Midvidy (Inactive)
            Reporter:
            adam.midvidy Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None