[SERVER-83408] DBClientSession/DBClientConnection constructor doesn't use so_timeout argument Created: 17/Nov/23 Updated: 06/Dec/23 Resolved: 06/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Vinod Kumar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Sprint: | Service Arch 2023-12-11 |
| Participants: |
| Description |
|
DBClientSession and DBClientConnection have constructors here and here that take an so_timeout argument. Presumably, this is intended to set the socket timeout for the connection, like the setSoTimeout member function does, but the argument is unused today. We should either correctly set the socket timeout or remove the constructor argument to avoid confusion |
| Comments |
| Comment by Vinod Kumar [ 06/Dec/23 ] |
|
Fixed the constructor issue. |
| Comment by Githook User [ 06/Dec/23 ] |
|
Author: {'name': 'Vinod Kumar', 'email': 'vinod.kumar@mongodb.com', 'username': 'vkumar-mdb'}Message: GitOrigin-RevId: 12c687ae3dce574cc5e1fac2e404c8de21f5addb |