-
Notifications
You must be signed in to change notification settings - Fork 357
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
Issue4810 #4823
Merged
Merged
Issue4810 #4823
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I set this as a draft because I am still investigating more. |
jbescos
force-pushed
the
issue4810
branch
4 times, most recently
from
July 9, 2021 06:24
740977f
to
85288ba
Compare
Signed-off-by: Jorge Bescos Gascon <jorge.bescos.gascon@oracle.com>
Signed-off-by: Jorge Bescos Gascon <jorge.bescos.gascon@oracle.com>
jbescos
force-pushed
the
issue4810
branch
5 times, most recently
from
July 9, 2021 14:10
7b51498
to
d9b1098
Compare
Signed-off-by: Jorge Bescos Gascon <jorge.bescos.gascon@oracle.com>
I am not able to reproduce any issue more but it is possible that there are more. |
senivam
approved these changes
Jul 19, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jansupol
approved these changes
Jul 26, 2021
This was referenced Sep 6, 2021
This was referenced Mar 8, 2022
1 task
1 task
Closed
1 task
Closed
1 task
1 task
This was referenced Oct 19, 2022
Closed
1 task
This was referenced Jan 6, 2023
Merged
This was referenced Feb 11, 2023
Closed
1 task
This was referenced May 11, 2023
This was referenced Jun 15, 2023
This was referenced Jul 6, 2023
1 task
This was referenced Apr 13, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This refers to the issue #4810
When there are many requests, some threads are blocked forever waiting for a CompletableFuture that is never completed. This is reproducible in the test. Usually this means one of these 2 possibilities:
In the original issue there are some errors related to:
Right after that method, the request should be completed, but this does not happen when there is that error.
With the test I saw that when the thread blocks forever, it is possible to see some leftovers in 'requestsInProgress':
These requestsInProgress are stored in a HashMap, and multiple threads can access it (for example in DestinationConnectionPool#getRequest and DestinationConnectionPool#processPendingRequests). I just changed it by a ConcurrentHashMap and I am not able to get the issue anymore.