Response issues/incomplete HTTP responses when servicing concurrent requests.

Open
#109 19 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api, backend

Research direction

Start with the integration test in the linked StressTest repository and reproduce the failure using two or three concurrent calls to the OData endpoint. Trace the responses and use the reported outcomes as the acceptance criteria: each response should be complete, non-empty, non-duplicated, and isolated from the others without unexpected 500 errors.

Written by the indexing model from the issue text.

Description

followup

Hi,

My team and I have noticed that when hitting an OData endpoint in parallel, the results returned seem to get scrambled, as though there is some kind of cross-talk between the responses.

The various outcomes we see are;

  • Everything is fine.
  • Response is a 200 OK, but content is incomplete.
  • Response is a 200 OK, but content is empty.
  • Responses is a 200 OK, but content contains duplication, or bits of another response.
  • Response is a 500 ERROR, and content is incomplete.

I have an integration test showing the failure in the repo here;
https://github.com/RobTF/AspNetCoreODataExamples/tree/master/StressTest

This seems like quite a major issue unless we are doing something drastically wrong in the setup. This seems to happen with even 2-3 concurrent calls to the server, so it's not a volume thing.

thanks,

Dominant language
C#
Stars
505
Forks
186
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OData/AspNetCoreOData

All issues in OData/AspNetCoreOData

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.