Request timed out

[dongzhaosheng73]

Description

The client occasionally sends System.TimeoutException: Request timed out
---> System.Threading.Tasks.TaskCanceledException: A task was canceled. The error client occasionally sends System.TimeoutException: Request timed out
---> System.Threading.Tasks.TaskCanceledException: A task was canceled. mistake.

Reproduction Steps

In random recurrence, either the client must be restarted or HttpClient must use a new socket.
I found that there were already similar problems but there was no practical solution.

restsharp/RestSharp#1092

Expected behavior

Request timed out should not affect subsequent request behavior

Actual behavior

Request timed out Subsequent requests will cause the Request timed out until the client restarts

Regression?

No response

Known Workarounds

No response

Configuration

.net 6
windows11
x86
RestSharp 108.0.2

Other information

No response

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[antonfirsov]

@dongzhaosheng73 this is not actionable for us with the information provided. Given the issue is RestSharp-specific and you also opened restsharp/RestSharp#2176, I think you will have better chances getting help there, but they would also need more information.

The best would be if you could provide a a repro. If it's not possible, detailed description of the client & server scenario with at least some code is still desired.

There is some chance that this might be related to .NET 6 connection pooling issues. Can you try if upgrading to .NET 8 solves the problem?

[antonfirsov]

Triage: moving to Future for now, in the unlikely case it turns out to be an unknown problem with HttpClient, we can bump the priority. Otherwise we should close.

[dotnet-policy-service]

This issue has been marked needs-author-action and may be missing some important information.

[alexeyzimarev]

I am not sure that the issue is related to RestSharp as RestSharp just forms a request message and sends it over via HttpClient.

[ManickaP]

Whether this is related to RestSharp or not doesn't change that fact that the issue as-is now is not actionable. We need a repro case, preferably just with HttpClient. Or traces, captures, logs from reporter's environment.

[alexeyzimarev]

What I meant is that the issue opened in RestSharp repository is not actionable as well as RestSharp's role is to create a request message and pass it over to HttpClient. My challenge is with "you will have better chances getting help there", as I don't think I can provide any help with the issue. Surely, I agree with your point that the issue that occurs in a specific environment, at random, is almost impossible to fix in lack of reliable repro.

[dotnet-policy-service]

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.