[ https://issues.apache.org/jira/browse/IGNITE-11113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758263#comment-16758263 ]
Artem Budnikov commented on IGNITE-11113: ----------------------------------------- [~dmagda] I reproduced the problem on my Linux machine. It occurs when JAVA_HOME is not set and you use Java version 10 or 11. In that case the script fails to detect the version of java and does not add the required startup parameters. When JAVA_HOME is set to the JAVA 11 directory, the script works as expected. For those who use `ignite.sh`, the most simple solution would be to set up the JAVA_HOME variable (instead of providing all the JVM options manually). I updated the documentation with that information. > JVM 9-11 startup parameters have to be mentioned in every section of getting > started > ------------------------------------------------------------------------------------ > > Key: IGNITE-11113 > URL: https://issues.apache.org/jira/browse/IGNITE-11113 > Project: Ignite > Issue Type: Task > Components: documentation > Reporter: Denis Magda > Assignee: Artem Budnikov > Priority: Blocker > > Ignite.sh fails on Mac OS with JDK 11. The following startup parameters [1] > have to be mentioned in callout blocks of every section in the getting > started guide [2] where it's explained how to start a node with ignite.sh or > launch an application. > The user has to know how to: > * Fix ignite.sh/ignite.bat to make them workable > * What to do in an IDEA like IntellijIdean and Eclipse to make examples and > apps workable > [1] > https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11 > [2] https://apacheignite.readme.io/docs/getting-started -- This message was sent by Atlassian JIRA (v7.6.3#76005)