ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
Date Wed, 13 Feb 2019 21:27:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767608#comment-16767608

Denis Magda commented on IGNITE-11155:

How about RuntimeMXBean solution? Check this thread:

> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -----------------------------------------------------------------------------
>                 Key: IGNITE-11155
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11155
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Dmitriy Pavlov
>            Assignee: Dmitriy Pavlov
>            Priority: Major
>             Fix For: 2.8
>         Attachments: start-java11-2.png, start-java11.png
>          Time Spent: 20m
>  Remaining Estimate: 0h
> In Ignite examples or using Ignite Embedded mode (using direct Ignition.start() call
from a user IDE), may fail with exceptions for JDKs newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to output
message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled. 
> See https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and Ignite in
embedded mode will show how to set up Application configuration 

This message was sent by Atlassian JIRA

View raw message