[CSHARP-2884] Async Socket methods do not use Socket.ReceiveTimeout Created: 18/Dec/19 Updated: 28/Oct/23 Resolved: 10/Jan/20 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 2.10.0 |
| Fix Version/s: | 2.10.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Stam | Assignee: | Robert Stam |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Case: | (copied to CRM) | ||||
| Description |
|
We have recently discovered in the .NET documentation that the async Socket methods do not use the Socket.SendTimeout and Socket.ReceiveTimeout values. Since our SDAM monitoring code uses async Socket operations (indirectly via async NetworkStream operations) the result is that any configuration of HeartbeatTimeout is not effective. The consequence is that SDAM can take longer than expected to re-discover a server that has been temporarily black-holed. |
| Comments |
| Comment by Githook User [ 13/Jan/20 ] |
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: |
| Comment by Githook User [ 13/Jan/20 ] |
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: |
| Comment by Githook User [ 10/Jan/20 ] |
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: |
| Comment by Githook User [ 10/Jan/20 ] |
|
Author: {'name': 'rstam', 'email': 'robert@robertstam.org', 'username': 'rstam'}Message: |
| Comment by Robert Stam [ 18/Dec/19 ] |
|
Link to the .NET documentation stating that ReceiveTimeout only applies to sync calls: |