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
Constant timeout errors #713
Comments
The stacktrace below:
|
Is there a possibility of landing into problems with apiman if I send a POST request without Content-Length header. |
Is anyone looking into it. We have checked that those 408 errors were caused by apiman. When we bypassed apiman, everything was working fine. Was happening for only few requests, not all. |
Apologies for slow responses. I can only work on Apiman in my spare time. Do the POST requests you describe actually take a very long period to execute? For example, sending a large payload? |
Regarding headers -- content-length or transfer-encoding:chunked would be expected. |
Thank you for the reply. No, the requests aren't huge, contain only 3 small fields. Although noticed that a few requests had Content-Length header missing. Not sure if exactly those requests landed into 408s. |
Hi
For one of our services, suddenly we started getting the following timeout errors in gateway.
The timeout period of 1000ms has been exceeded while executing GET /v0/....
The timeout period of 1000ms has been exceeded while executing POST /v0/...
Just as we restarted the gateway, it started working.
Happened for only one service, the rest were working fine.
Please help figure out the cause behind.
Noticed a few 408 errors in the nginx logs of service but why would gateway hang due to that when we have connect & read timeouts in place (1s each)
The text was updated successfully, but these errors were encountered: