|
||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The actual issue is that if a thread that's making a remote call through a type-safe proxy gets interrupted, and if the method that's being called doesn't have "throws InterruptedException", then the proxy code throws UndeclaredThrowableException as opposed to the raw InterruptedException.
Since JVM does allow an undeclared checked exception to be thrown (even though javac won't allow it), it would have been better for us if the InterruptedException gets thrown directly, which then gets caught and handled properly.
While this happens more often in node monitors, as they tend to make calls on nodes that may be hanging, this is actually an universal problem. So I'm adjusting the summary accordingly.
Fixing this that way would require us to find a better proxy library. Alternatively, we can wrap it in something like RequestAbortedException after checking if the signature allows InterruptedException.