We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Intermittently few api calls gets closed with the following error Error: IncompleteMessage: connection closed before message completed.
Error: IncompleteMessage: connection closed before message completed
The application should either kept the connection alive or retry connection.
The application is closing the connection and failing the API call Detailed hyper create issue: hyperium/hyper#2136
Let the application receive more load. For me, for every 1000 transactions, received one failure with this error.
Not able to talk to connector[basically it can be any outgoing call].
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.
x-request-id
If not (or if building/running locally), please provide the following details:
rustc --version
rustc 1.74.0
cargo r --features vergen -- --version
router 2024.01.08.0-75-gae83f28-ae83f28-2024-01-23T09:47:32.000000000Z
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
inventvenkat
Successfully merging a pull request may close this issue.
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:
rustc --version
):rustc 1.74.0
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?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: