-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8297424: java/net/httpclient/AsyncExecutorShutdown.java fails in AssertionError due to misplaced assert #11332
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
Conversation
|
👋 Welcome back dfuchs! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
Hello Daniel, the change where we move the assert into the synchronized block looks fine to me. Looking at the code I think the check to see that the This PR also has changes in the |
These are changes I made when investigating the fix, and they are not related. The |
… conditions with ternary operators
jaikiran
left a comment
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 Daniel. The latest changes look good to me.
|
@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 9 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 5d2772a.
Your commit was automatically rebased without conflicts. |
The
ResponseSubscribers.HttpResponseInputStreamclass has an assert that has been observed firing (rarely) when running thejava/net/httpclient/AsyncExecutorShutdown.javatest.After a thorough analysis of the code and the log failure I am convinced that the issue is due to a misplaced assert.
If cancellation happens asynchronously while the subscriber is being subscribed with the lower layers of the stack, the
HttpResponseInputStreammight get closed and theLAST_LISTbuffer might be offered afterclosed == falsehas been observed by theonSubscribedmethod, but before the assertion has been checked. The assertion assumes that the queue must be empty, but it might not ifclosehas been called and theLAST_LISTbuffer has been offered.Moving the assert from within the synchronized block, to ensure that the observed value of
closedis consistent with the state of the queue, should fix it. I have tagged the bug asnoreg-hard, I'm not sure it would be fair to say thatAsyncExecutorShutdown.javacan be used to verify the fix.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/11332/head:pull/11332$ git checkout pull/11332Update a local copy of the PR:
$ git checkout pull/11332$ git pull https://git.openjdk.org/jdk pull/11332/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 11332View PR using the GUI difftool:
$ git pr show -t 11332Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/11332.diff