/// <summary>
/// Amount of time the polling service will wait for a request from an RPC call.
/// Specifically the amount of time to wait for the first byte of the request to arrive.
///
/// This value must never be less than the PollingQueueWaitTimeout, of the client, since this
/// is the timeout of the long poll the polling service makes to the client to get the next request.
///
/// Currently set to 10 minutes as that is what the timeout used to be.
/// </summary>
public TimeSpan TcpClientReceiveRequestTimeoutForPolling { get; set; } = TimeSpan.FromMinutes(10);
Which will allow as to reduce the time the polling service will wait for the beginning of a Response message to be received since we know the polling queue will send null messages every 30s if it has no Requests to make. This makes it possible to have the service more readily detect a stalled connection.
This value only makes sense to be set in the polling service.
How to review this PR
Quality :heavy_check_mark:
Pre-requisites
[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.
Background
[[SC-59505]]
Adds timeout:
Which will allow as to reduce the time the polling service will wait for the beginning of a
Response
message to be received since we know the polling queue will sendnull
messages every30s
if it has no Requests to make. This makes it possible to have the service more readily detect a stalled connection.This value only makes sense to be set in the polling service.
How to review this PR
Quality :heavy_check_mark:
Pre-requisites