-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8201183: sjavac build failures: "Connection attempt failed: Connection refused" #18712
Conversation
👋 Welcome back djelinski! A progress list of the required criteria for merging this PR into |
@djelinski 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 34 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@djelinski The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
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.
Thank you very much for spending the time and effort of fixing these intermittent javac server issues!
Thanks for the reviews! /integrate |
Going to push as commit ecc603c.
Your commit was automatically rebased without conflicts. |
@djelinski Pushed as commit ecc603c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The "Connection attempt failed: Connection refused" error may happen if the client tries to connect to a server that is no longer listening, which in turn may happen if the server shuts down without removing the port file. I added a check that the delete operation succeeded, and retry as necessary.
I removed the comment about asynchronous deletes on Windows. I don't think it's correct; it's more likely that the file existed because the delete operation failed.
I added a 1 second delay after deleting the port file; this delay is intended to allow any clients that managed to read the port file before it was deleted to finish connecting. It should also take care of the "IOException caught during compilation: Connection reset" issue.
And finally, the portfile is now closed when not in use. This was necessary to fix the failures on Windows, where the file cannot be deleted as long as it is open in any process.
In order to verify the fix, I modified
IdleMonitor.KEEPALIVE
to 1 second. Without the changes from this PR this resulted in at least a few failures in every mach5 run. With this PR I was able to build tier1-5 with no failures.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18712/head:pull/18712
$ git checkout pull/18712
Update a local copy of the PR:
$ git checkout pull/18712
$ git pull https://git.openjdk.org/jdk.git pull/18712/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18712
View PR using the GUI difftool:
$ git pr show -t 18712
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18712.diff
Webrev
Link to Webrev Comment