This appears to be related to using the latest v7.5.1. Stability of the connection seems to be fine as long as the client is alive. This was never an observed issue with 7.4 and below, though that is conjecture. Another possible culprit may be a newer, later version of the .NET Framework.
Since we're not in control of either of those circumstances, we have to find a way to mitigate the issue in the HFM code.
Observed interactions with the underlying NetworkStream where read or write requests are now throwing an IOException after a client connection is closed or lost. In those cases, handle the exception and Connection.Close() so HFM reacts gracefully.
This appears to be related to using the latest v7.5.1. Stability of the connection seems to be fine as long as the client is alive. This was never an observed issue with 7.4 and below, though that is conjecture. Another possible culprit may be a newer, later version of the .NET Framework.
Since we're not in control of either of those circumstances, we have to find a way to mitigate the issue in the HFM code.
Observed interactions with the underlying NetworkStream where read or write requests are now throwing an IOException after a client connection is closed or lost. In those cases, handle the exception and Connection.Close() so HFM reacts gracefully.