You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/20 09:08:20 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15506107#comment-15506107 ]
ASF GitHub Bot commented on IGNITE-3926:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1087
IGNITE-3926: Exception thrown from static job initializer hangs remote future.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3926
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1087.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 #1087
----
commit 8fc5092610865e80d81b86b50b4ecfc0921b67ff
Author: Andrey V. Mashenkov <an...@gmail.com>
Date: 2016-09-19T16:01:09Z
Fixed
commit 7e5b51486ccff375b943f6ce2e1bc5505d39400e
Author: Andrey V. Mashenkov <an...@gmail.com>
Date: 2016-09-19T16:27:11Z
Fixed similar bug inTasksProcessor
commit d930866b5bc49f057dddeeb4a2548ae83a0810b2
Author: Andrey V. Mashenkov <an...@gmail.com>
Date: 2016-09-20T09:07:51Z
Minor fixes
----
> 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: Andrew Mashenkov
> Fix For: 1.8
>
>
> 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.3.4#6332)