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

Anton Vinogradov updated IGNITE-4618:
-------------------------------------
    Fix Version/s:     (was: 1.9)
                   2.0

FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.

> 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: 2.0
>
>
> *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)

Reply via email to