[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758393#comment-16758393
]
Ignite TC Bot commented on IGNITE-11155:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2972545]]
* IgniteSpiTestSuite:
TcpClientDiscoverySpiFailureTimeoutSelfTest.testPingFailedClientNode - 0,0%
fails in last 407 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2963881&buildTypeId=IgniteTests24Java8_RunAll]
> 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
>
> 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
(v7.6.3#76005)
