Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 1 Feb 2017 14:40:52 +0000 (UTC)
From: "Igor Sapego (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13038095.1485433256000.8181.1485960052387@Atlassian.JIRA>
In-Reply-To: <JIRA.13038095.1485433256000@Atlassian.JIRA>
References: <JIRA.13038095.1485433256000@Atlassian.JIRA> <JIRA.13038095.1485433256837@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (IGNITE-4618) CPP: Do not start JVM if it is
 already started
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Feb 2017 14:40:59 -0000


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

Igor Sapego reassigned IGNITE-4618:
-----------------------------------

    Assignee:     (was: Igor Sapego)

> CPP: Do not start JVM if it is already started
> ----------------------------------------------
>
>                 Key: IGNITE-4618
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4618
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.8
>            Reporter: Vladimir Ozerov
>             Fix For: 1.9
>
>
> *Problem*
> Consider the following scenario:
> 1) User's app started JVM in the process somehow.
> 2) User tries to start the node. 
> 3) Result: exception.
> *Solution*
> We need to check if JVM is already started. If yes - then try re-using. Note that we are likely to fail at this point because user might forgot to pass proper Ignite classpath. In this case we must throw extremely sensible exception, so that user understand how to fix the problem right away. 
> E.g.: "Failed to start Ignite node with already started JVM due to invalid classpath; please add the following JARs to the classpath: [PATH TO IGNITE_HOME JARS]".


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)