You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/07/10 07:58:01 UTC

[jira] [Updated] (IGNITE-3926) Exception thrown from static job initializer hangs remote future.

     [ https://issues.apache.org/jira/browse/IGNITE-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov updated IGNITE-3926:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> Exception thrown from static job initializer hangs remote future.
> -----------------------------------------------------------------
>
>                 Key: IGNITE-3926
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3926
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>    Affects Versions: 1.7
>            Reporter: Vladimir Ozerov
>            Assignee: Yakov Zhdanov
>             Fix For: 2.2
>
>
> Test case:
> 1) Create a job/closure class with static initializer. Throw some exception from it (good candidate is {{NoClassDefFoundError}} which simulates a dependency which is missing at runtime).
> 2) Start standalone Ignite node.
> 3) Try to running a job on this node from remote process.
> 4) Observe that a future in remote process hangs because the first node fails to process error correctly.
> Proposed fix:
> We need to improve our error handling for our {{GridJobExecuteRequest}}. Possibly adding additional try-catch ensuring that no exceptions/errors are ignored.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)