[jira] [Updated] (IGNITE-3271) Can't start a node with default config when no pause (-np) parameter is set

["Pavel Tupitsyn (JIRA)" <ji...@apache.org>]

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

Pavel Tupitsyn updated IGNITE-3271:
-----------------------------------
    Fix Version/s:     (was: 1.7)
                   1.8

> Can't start a node with default config when no pause (-np) parameter is set
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-3271
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3271
>             Project: Ignite
>          Issue Type: Bug
>          Components: community
>    Affects Versions: 1.6
>            Reporter: Denis Magda
>             Fix For: 1.8
>
>
> If to start an Ignite instance with "-np" argument then the node is not able to start with the exception below.
> {code}
> ./ignite.sh -np
> Invalid arguments: -np
> Usage:
>    ./ignite.sh [?]|[path {-v}{-np}]|[-i]
>    Where:
>    ?, /help, -help, - show this message.
>    -v               - verbose mode (quiet by default).
>    -np              - no pause on exit (pause by default)
>    -nojmx           - disable JMX monitoring (enabled by default)
>    -i              - interactive mode (choose configuration file from
> list).
>    path            - path to Spring XML configuration file.
>                      Path can be absolute or relative to IGNITE_HOME.
> Spring file should contain one bean definition of Java type
> 'org.apache.ignite.configuration.IgniteConfiguration'. Note that bean will
> be
> fetched by the type and its ID is not used./
> {code}
> However if to set a configuration file parameter then everything will work fine
> {code}
> ./ignite.sh -np ../examples/config/example-ignite.xml 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)