[ https://issues.apache.org/jira/browse/IGNITE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409550#comment-16409550 ]
ASF GitHub Bot commented on IGNITE-7904: ---------------------------------------- GitHub user slukyano opened a pull request: https://github.com/apache/ignite/pull/3683 IGNITE-7904: Changed IgniteUtils::cast not to trim exception chains. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7904 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3683.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3683 ---- ---- > ComputeTaskFuture.get() throws incorrect exception if ComputeTask.result() > throws IgniteException > ------------------------------------------------------------------------------------------------- > > Key: IGNITE-7904 > URL: https://issues.apache.org/jira/browse/IGNITE-7904 > Project: Ignite > Issue Type: Bug > Reporter: Stanislav Lukyanov > Assignee: Stanislav Lukyanov > Priority: Major > > ComputeTask.result() javadoc says: "Throws: IgniteException - If handling a > job result caused an error effectively rejecting a failover. This exception > will be thrown out of ComputeTaskFuture.get() method." > However, GridFutureAdapter calls IgniteUtils.cast(Throwable) on the exception > before throwing it from get(), and the latter method trims the stack trace to > the first occurence of an IgniteCheckedException. Because of that, get() > throws not the IgniteException thrown from the ComputeTask.result() but one > of its causes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)