Skip to content
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

8347491: IllegalArgumentationException thrown by ThreadPoolExecutor doesn't have a useful message #23081

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

viktorklang-ora
Copy link
Contributor

@viktorklang-ora viktorklang-ora commented Jan 13, 2025

Seems sensible to improve this given that it can be tricky to figure out which parameter caused the exception to be thrown.


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-8347491: IllegalArgumentationException thrown by ThreadPoolExecutor doesn't have a useful message (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 23081

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@viktorklang-ora
Copy link
Contributor Author

@DougLea This is the PR I was talking about earlier today.

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 13, 2025

👋 Welcome back vklang! 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 Jan 13, 2025

@viktorklang-ora This change is no longer ready for integration - check the PR body for details.

@openjdk openjdk bot added the rfr Pull request is ready for review label Jan 13, 2025
@openjdk
Copy link

openjdk bot commented Jan 13, 2025

@viktorklang-ora The following label will be automatically applied to this pull request:

  • core-libs

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@mlbridge
Copy link

mlbridge bot commented Jan 13, 2025

Webrevs

@DougLea
Copy link
Contributor

DougLea commented Jan 13, 2025

Thanks for doing this. Looks good to me.

Copy link
Contributor

@AlanBateman AlanBateman left a comment

Choose a reason for hiding this comment

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

Looks fine, just wondering if the tests for IAE should check there is a message.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jan 13, 2025
@liach
Copy link
Member

liach commented Jan 13, 2025

There's a contributor PR from the java bugs submitter at #23050, I wonder what we should do in this case.

@He-Pin
Copy link

He-Pin commented Jan 13, 2025

#23050

There is already a pr for this:)
As I encountered this in production

And seems the OCA is waiting for processing.
image

@AlanBateman
Copy link
Contributor

There's a contributor PR from the java bugs submitter at #23050, I wonder what we should do in this case.

The PR has the "oca" label so we can't look or comment on it.

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-libs [email protected] rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

5 participants