Andrey N. Gura created IGNITE-15408:
---------------------------------------
Summary: CLI: 'ignite node start' command produces NPE when
optional config path is not passed
Key: IGNITE-15408
URL: https://issues.apache.org/jira/browse/IGNITE-15408
Project: Ignite
Issue Type: Bug
Reporter: Andrey N. Gura
CLI command {{ignite node start}} produces {{NullPointerException}} in case
when optional {{--config=<configPath>}} parameter is not passed.
*Steps to reproduce:*
1. {{ignite init}}
2. {{ignite node start prb-node}}
*Result:*
{noformat}
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
-Djava.net.preferIPv4Stack=true
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Starting a new Ignite node...
Can't start the node. Read logs for details:
<path-to-log>/ignite-log/prb-node.log
{noformat}
*Log:*
{noformat}
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
-Djava.net.preferIPv4Stack=true
Exception in thread "main" java.lang.NullPointerException
at org.apache.ignite.app.IgniteCliRunner.main(IgniteCliRunner.java:59)
{noformat}
*Expected behavior:*
Node should be started with some defaults or {{--config}} parameter must be
mandatory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
