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
8264048: Fix caching in Jar URL connections when an entry is missing #3263
Conversation
|
@AlekseiEfimov 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. |
Webrevs
|
Hi Aleksei, thanks for putting this together.
Otherwise the proposed changes look good to me. |
Thanks for the review, Daniel. It is correct that |
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.
Hi, Aleksei. The change looks good.
@AlekseiEfimov This change now passes all automated pre-integration checks. 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 87 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.
|
/contributor add dfuchs |
@AlekseiEfimov |
/integrate |
@AlekseiEfimov Since your change was applied there have been 88 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a611c46. |
Current fix tries to tackle an issue with URL connection referencing non-existing Jar file entries:
If an entry that doesn't exist is specified in an URL connection the underlying Jar file is still cached even if an exception is thrown after that. Such behavior prevents the caller, for instance, a
URLClassLoader
, from closing a Jar file.The proposed fix checks if entry exists before caching a Jar file (only for cases with enabled caching):
The following tests have been used to verify the fix:
:jdk_core:
testsapi/java_util
,api/java_net
JCK testsProgress
Issue
Reviewers
Contributors
<dfuchs@openjdk.org>
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3263/head:pull/3263
$ git checkout pull/3263
Update a local copy of the PR:
$ git checkout pull/3263
$ git pull https://git.openjdk.java.net/jdk pull/3263/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3263
View PR using the GUI difftool:
$ git pr show -t 3263
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3263.diff