Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Mon, 19 Sep 2016 09:50:20 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13005863.1474278560000.603821.1474278620523@Atlassian.JIRA>
In-Reply-To: <JIRA.13005863.1474278560000@Atlassian.JIRA>
References: <JIRA.13005863.1474278560000@Atlassian.JIRA> <JIRA.13005863.1474278560876@arcas>
Subject: [jira] [Created] (IGNITE-3926) Exception thrown from static job
 initializer hangs remote future.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 19 Sep 2016 09:50:22 -0000

Vladimir Ozerov created IGNITE-3926:
---------------------------------------

             Summary: 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)