Closed stephenlautier closed 4 years ago
You're migrating to .NET Core 3.0 -- were you previously using .NET Core 2.x, or are you coming from .NET Framework 4.x?
"The response ended prematurely" indicates that HttpClient was expecting X bytes in a response and the connection was closed by the server before it could read all of them.
Are you able to reduce this behavior into a small repro?
Sorry for not writing it, thought I did, We were netcore 2.x (specifically 2.2.1).
Unfortunately, the only 2 cases which we produce are work projects; Tried to produce one of them in a new project but didn't produce it, obviously our apps are much heavier than an empty project, and it seems when there are a lot in concurrency the failures increase.
Some extra info perhaps it helps... In the second scenario we produce around 1mb HTML (which is quite big) from SSR (node) > dotnet and takes from 1.5sec - 6sec to fully complete - when i was "load" testing it, with 120 requests 40 concurrent was getting around ~4 failures (sometimes more) however when we decrease the concurrency to around 15 it was much more successful
@stephenlautier Same problem when rendering on nodejs but we use Jering.Javascript.NodeJS I think problem in nodejs server
@DaniilSokolyuk we get this even when we do not have any nodejs tho like the e2e scenario which i mentioned (error 1)
Triage: To make it actionable we need a small repro (without NodeJS server to avoid server problems). Closing as it is not available and not actionable now. Feel free to reopen when you have the repro for us. Thanks!
After updating to netcore 3 we are getting several issues with the HttpClient, failing randomly - we have 2 scenarios which fails "similarly" in different projects.
Error 1
This is a running E2E test project performing a lot of HttpClient to call Api's and randomly a call fails, sometimes they do all work correctly.
Error 2
This is an aspnet project with SSR for angular - calls to node via aspnet node services, when adding a little bit of load they start failing randomly with this error.
We are using