We definitely don’t want to send more heartbeats, they’re sent too often as it is, but you can adjust how often it’s sent and when to consider the request as broken with the HeartbeatInterval and IdleTimeout properties on ServerEventsFeature, they default to 10s / 30s.
If the connection is aborted it could either be your network is unhealthy and is dropping packets and not acknowledging http/network requests. Another issue that can cause HttpWebRequests to hang is if you use the Web Request elsewhere and aren’t disposing of it properly since .NET uses the same pool under the hood and only allows a few concurrent connections per host which you can adjust with:
ServicePointManager.DefaultConnectionLimit = n;
If that doesn’t help can you make sure all your Request DTOS hav IReturn or IReturnVoid interface marker as it will prevent clients from returning a HttpWebRequest instance that would need to be explicitly disposed as explained in this Thread.