Async Socket methods do not use Socket.ReceiveTimeout

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.10.1
    • Affects Version/s: 2.10.0
    • Component/s: Connectivity
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Robert Stam
            Reporter:
            Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: