-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
8269258: java/net/httpclient/ManyRequestsLegacy.java failed with connection timeout #6740
Conversation
👋 Welcome back dfuchs! A progress list of the required criteria for merging this PR into |
Webrevs
|
}); | ||
} | ||
boolean done = false; | ||
LOOP: do { |
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.
Could we add a comment here indicating the purpose of the loop in terms of catching ConnectException (only) and what happens in terms of the reduction of the request concurrency?
}); | ||
} | ||
boolean done = false; | ||
LOOP: do { |
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.
same comment as for ManyRequests
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
@dfuch This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 2 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit 37921e3.
Your commit was automatically rebased without conflicts. |
The three tests:
have been observed failing intermittently with ConnectException on windows 10 machines in our CI.
These tests open 20 concurrent requests each, and the suspicion is that when these tests run concurrently on the same machine they may cross some OS throttling threshold that causes the connection to be rejected.
The tests had a built-in mechanism to throttle the number of requests running concurrently, but it was not used.
The fix is to enable this mechanism on windows, limiting the concurrency to 10 requests, if the first run of the test fails with a ConnectException.
With this in place I am no longer observing any failure (was 1 to 3 failures for every 50 runs before)
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6740/head:pull/6740
$ git checkout pull/6740
Update a local copy of the PR:
$ git checkout pull/6740
$ git pull https://git.openjdk.java.net/jdk pull/6740/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6740
View PR using the GUI difftool:
$ git pr show -t 6740
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6740.diff