[
https://issues.apache.org/jira/browse/IGNITE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427068#comment-16427068
]
Stanislav Lukyanov commented on IGNITE-7904:
--------------------------------------------
Confirmed tests pass:
Compute (Grid):
https://ci.ignite.apache.org/viewLog.html?buildId=1181097&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ComputeGrid
Java Client:
https://ci.ignite.apache.org/viewLog.html?buildId=1181095&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
Cache (Restarts) seems to fail with timeout error in different branches:
https://ci.ignite.apache.org/viewLog.html?buildId=1181083&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_CacheRestarts1
https://ci.ignite.apache.org/viewLog.html?buildId=1178979&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_CacheRestarts1
> 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)
