[
https://issues.apache.org/jira/browse/IGNITE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426904#comment-16426904
]
Stanislav Lukyanov commented on IGNITE-7904:
--------------------------------------------
I don't think this change can cause timeout errors in tests. I've checked the
IgniteBinaryObjectsComputeGridTestSuite:
GridMultinodeRedeployPrivateModeSelfTest.testPrivateMode - it passes. I'll
rerun TC to confirm.
> 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
> Fix For: 2.5
>
>
> 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)
