[
https://issues.jboss.org/browse/WFCORE-4617?page=com.atlassian.jira.plugi...
]
Bartosz Spyrko commented on WFCORE-4617:
----------------------------------------
Currently any argument that doesn't match accepted parameters is treated as a CLI
command.
I think it should be safe to assume that an argument that starts with "--" might
be a misspelled parameter and display an "Unsupported parameter" error or at
least a warning. [~jfdenise] WDYT?
jboss-cli.sh does not error on invalid options such as --controler
------------------------------------------------------------------
Key: WFCORE-4617
URL:
https://issues.jboss.org/browse/WFCORE-4617
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Bartosz Spyrko
Assignee: Bartosz Spyrko
Priority: Minor
If the --controller is not spelled correctly, the CLI is ignoring it and then trying to
connect to the default localhost:9990 in from the jboss-cli.xml. This makes it look like
there is a connection error when the actual issue is the option passed to the CLI is not a
valid option.
{code}
./bin/standalone.sh -Djboss.socket.binding.port-offset=9
{code}
{code}
/bin/jboss-cli.sh --controler=myhost:9999 --connect
Failed to connect to the controller: The controller is not available at localhost:9990:
java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990.
The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The
connection failed: Connection refused
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)