Skip to content

8362581: Timeouts in java/nio/channels/SocketChannel/OpenLeak.java on UNIX #26478

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

Closed

Conversation

Michael-Mc-Mahon
Copy link
Member

@Michael-Mc-Mahon Michael-Mc-Mahon commented Jul 25, 2025

Hi,

This is a fix for 8362581 caused by the implementation for https://bugs.openjdk.org/browse/JDK-8348986
An incorrect check was added to the method Exceptions.ioException() which wasn't noticed partly
because that file was renamed, and webrev doesn't show the diffs side by side.
The effect of this change is to restore the method to pretty much what it was before, but taking account
of the changed categorisation of exceptions.

A test is not included since this was caught by an existing regression test.

Thanks,
Michael


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8362581: Timeouts in java/nio/channels/SocketChannel/OpenLeak.java on UNIX (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26478/head:pull/26478
$ git checkout pull/26478

Update a local copy of the PR:
$ git checkout pull/26478
$ git pull https://git.openjdk.org/jdk.git pull/26478/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26478

View PR using the GUI difftool:
$ git pr show -t 26478

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26478.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 25, 2025

👋 Welcome back michaelm! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jul 25, 2025

@Michael-Mc-Mahon 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:

8362581: Timeouts in java/nio/channels/SocketChannel/OpenLeak.java on UNIX

Reviewed-by: jpai, alanb, djelinski

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 3 new commits pushed to the master branch:

  • 9e209fe: 8364110: Remove unused methods in GCCause
  • 75ff7e1: 8361712: Improve ShenandoahAsserts printing
  • 06fdb61: 8361964: Remove outdated algorithms from requirements and add PBES2 algorithms

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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 master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Jul 25, 2025

@Michael-Mc-Mahon The following labels will be automatically applied to this pull request:

  • core-libs
  • nio

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.

@Michael-Mc-Mahon Michael-Mc-Mahon marked this pull request as ready for review July 25, 2025 12:11
@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 25, 2025
@mlbridge
Copy link

mlbridge bot commented Jul 25, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 25, 2025
@AlanBateman
Copy link
Contributor

/label remove core-libs
/label add net

@openjdk
Copy link

openjdk bot commented Jul 25, 2025

@AlanBateman
The core-libs label was successfully removed.

@openjdk
Copy link

openjdk bot commented Jul 25, 2025

@AlanBateman
The net label was successfully added.

@@ -22,7 +22,7 @@
*/

/* @test
* @bug 6548464
* @bug 6548464 8362581
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can drop this change to the test, it only accidentally uncovered this issue.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jul 25, 2025
Copy link
Member

@jaikiran jaikiran left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I've verified that with this change, the timing for the test methods in test/jdk/java/nio/channels/SocketChannel/OpenLeak.java drops back to the same duration that was there before the changes that were done in https://bugs.openjdk.org/browse/JDK-8348986

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 25, 2025
@Michael-Mc-Mahon
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented Jul 26, 2025

Going to push as commit de59da2.
Since your change was applied there have been 6 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 26, 2025
@openjdk openjdk bot closed this Jul 26, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jul 26, 2025
@openjdk
Copy link

openjdk bot commented Jul 26, 2025

@Michael-Mc-Mahon Pushed as commit de59da2.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

4 participants