Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: IncompleteMessage: connection closed before message completed #3428

Closed
2 tasks done
inventvenkat opened this issue Jan 23, 2024 · 0 comments · Fixed by #3426
Closed
2 tasks done

Error: IncompleteMessage: connection closed before message completed #3428

inventvenkat opened this issue Jan 23, 2024 · 0 comments · Fixed by #3426
Assignees
Labels
C-bug Category: Bug

Comments

@inventvenkat
Copy link
Contributor

Bug Description

Intermittently few api calls gets closed with the following error Error: IncompleteMessage: connection closed before message completed.

Expected Behavior

The application should either kept the connection alive or retry connection.

Actual Behavior

The application is closing the connection and failing the API call
Detailed hyper create issue: hyperium/hyper#2136

Steps To Reproduce

Let the application receive more load. For me, for every 1000 transactions, received one failure with this error.

Context For The Bug

Not able to talk to connector[basically it can be any outgoing call].

Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:

  1. Operating System : Linux ubuntu
  2. Rust version (output of rustc --version): rustc 1.74.0
  3. App version (output of cargo r --features vergen -- --version): router 2024.01.08.0-75-gae83f28-ae83f28-2024-01-23T09:47:32.000000000Z

Have you spent some time checking if this bug has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@inventvenkat inventvenkat added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Jan 23, 2024
@inventvenkat inventvenkat self-assigned this Jan 23, 2024
@inventvenkat inventvenkat linked a pull request Jan 23, 2024 that will close this issue
15 tasks
@SanchithHegde SanchithHegde removed the S-awaiting-triage Status: New issues that have not been assessed yet label Feb 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants