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

Capturing runtime exceptions from Computer.threadPoolForRemoting.submit(Runnable) #7284

Merged
merged 2 commits into from
Nov 23, 2022

Conversation

jglick
Copy link
Member

@jglick jglick commented Oct 20, 2022

Spent a while trying to track down an issue which turned out to be an unchecked exception thrown out of JnlpConnectionStateListener.afterChannel and swallowed by FutureTask, which ExceptionCatchingThreadFactory does not address.

Proposed changelog entries

  • Developer: better error logging for unexpected problems in Computer.threadPoolForRemoting.

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least two (2) approvals for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
  • Proper changelog labels are set so that the changelog can be generated automatically.
  • If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@jglick jglick requested a review from Vlatombe October 20, 2022 18:04
@NotMyFault NotMyFault added the developer Changes which impact plugin developers label Oct 20, 2022
Co-authored-by: Alexander Brandes <brandes.alexander@web.de>
@@ -131,9 +131,12 @@ protected void opened() {
LOGGER.fine(() -> "setting up channel for " + agent);
state.fireBeforeChannel(new ChannelBuilder(agent, Computer.threadPoolForRemoting));
transport = new Transport();
state.fireAfterChannel(state.getChannelBuilder().build(transport));
LOGGER.fine(() -> "set up channel for " + agent);
return null;
Copy link
Member Author

Choose a reason for hiding this comment

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

This was coercing the lambda to a Callable based on the checked exception.

@NotMyFault NotMyFault requested a review from a team November 7, 2022 09:47
Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

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

/label ready-for-merge


This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

@comment-ops-bot comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Nov 7, 2022
@NotMyFault
Copy link
Member

@Vlatombe do you mind taking a look, please? I was holding off a merge, because Jesse requested your explicit review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer Changes which impact plugin developers ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback
Projects
None yet
4 participants