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

long polling API return error #230

Open
five111 opened this issue Nov 30, 2021 · 5 comments
Open

long polling API return error #230

five111 opened this issue Nov 30, 2021 · 5 comments

Comments

@five111
Copy link

five111 commented Nov 30, 2021

测试watch接口 预期返回304

http://127.0.0.1:30110/v1/default/kie/kv?label=app:app11446&label=func:func784&wait=60s

实际返回

image

不加wait 返回正常

image

@five111
Copy link
Author

five111 commented Nov 30, 2021

似乎超过wait参数超过60s就会这样?60s以下看着很正常
image

@five111
Copy link
Author

five111 commented Nov 30, 2021

@tianxiaoliang @little-cui

@tianxiaoliang
Copy link
Contributor

will verify

@tianxiaoliang
Copy link
Contributor

you should check your testing tool settings about http timeout param, may be it is too short

@tianxiaoliang tianxiaoliang changed the title watch接口失效 long polling API return error Nov 30, 2021
@five111
Copy link
Author

five111 commented Dec 1, 2021

This phenomenon still occurs when I use Google Chrome or curl commands.
I’m not sure if it’s because I did a 2000-thread stress test on kie before.
Now it’s been a day since the stress test. It seems that the phenomenon still exists.
When debugging, the logic processing is normal.
rctx.WriteHeader(http.StatusNotModified) is indeed executed, but the problem I described will appear when return.
Today I will try to perform a stress test on Linux to observe this phenomenon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants