-
Notifications
You must be signed in to change notification settings - Fork 34
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
Pending Connections exceeding Max Pending Limit #121
Comments
@daanishsarguru I have an improvement in #122, but it still isn't 100% perfect. BUT it seems in your test you have unbounded growth, and with the fix I expect there will be an upper bound now, much closer to the configured |
I'll close this through #122 @daanishsarguru I've also created #123 as a follow-up to keep track of the fact that |
Thanks @simonbasle 👌 |
We have a Spring Boot project which uses reactor-netty for WebClient which is dependent on reactor-pool.
We're using WebClient to make API calls and facing an issue wherein Webclient is exceeding the max acquire queue size.
We have set the pendingAcquireMaxCount to 10000, however from the graphs, it can be seen that it has increased much beyond that
Expected Behavior
The extra requests should've failed with PoolAcquirePendingLimitException exception
Actual Behavior
Pending Requests keep on increasing without check, and none of the request actually gets processed, all of them keep timing out. I have tested this with a service we call by giving it a very large timeout (1 minute)
Steps to Reproduce
Unfortunately, I haven't been able to reproduce this on my local machine. I've only been able to witness this on the production environment randomly on some of the running instances
Possible Solution
I'm suspecting this has something to do with the following method
If somehow the PENDING_COUNT value were to exceed maxPending, this issue is set into motion
Environment
Reactor version(s) used:
reactor-netty: 0.9.16.RELEASE
reactor-pool: 0.1.8.RELEASE
Spring Boot: 2.2.10.RELEASE
JVM version: openjdk version "1.8.0_211-b12"
OS and version: alpine:3.6
The text was updated successfully, but these errors were encountered: