[SERVER-20624] NetworkInterfaceASIO does not always initialize messageId and responseTo Created: 24/Sep/15  Updated: 07/Oct/15  Resolved: 24/Sep/15

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Adam Midvidy Assignee: Adam Midvidy
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platform A (10/09/15)
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'amidvidy', u'name': u'Adam Midvidy', u'email': u'amidvidy@gmail.com'}

Message: SERVER-20624 always initialize messageId and responseTo on outgoing requests in NetworkInterfaceASIO
Branch: master
https://github.com/mongodb/mongo/commit/7efa986ccf86e858a7115d4cdd2c36bfddcf5fb9

Generated at Thu Feb 08 03:54:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.