Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 2 Aug 2016 22:33:20 +0000 (UTC)
From: "Valentin Kulichenko (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12984545.1467157989000.205225.1470177200786@Atlassian.JIRA>
In-Reply-To: <JIRA.12984545.1467157989000@Atlassian.JIRA>
References: <JIRA.12984545.1467157989000@Atlassian.JIRA> <JIRA.12984545.1467157989907@arcas>
Subject: [jira] [Updated] (IGNITE-3392) IgniteServices.deploy() method
 doesn't throw exception in case service initialization throws exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 Aug 2016 22:33:22 -0000


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

Valentin Kulichenko updated IGNITE-3392:
----------------------------------------
    Fix Version/s:     (was: 1.7)
                   2.0

> IgniteServices.deploy() method doesn't throw exception in case service initialization throws exception
> ------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3392
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3392
>             Project: Ignite
>          Issue Type: Bug
>          Components: managed services
>    Affects Versions: 1.6
>            Reporter: Valentin Kulichenko
>            Assignee: Alexander Paschenko
>             Fix For: 2.0
>
>         Attachments: Test.java
>
>
> Test that demonstrates the issue is attached. If exception is thrown from the {{Service.init()}} method, it's only printed out on the server not propagated to the client. If client then tries to get the proxy, it goes to infinite loop.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)