Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4617

jboss-cli.sh does not error on invalid options such as --controler

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 10.0.0.Beta6, 10.0.0.Final
    • None
    • CLI
    • None

    Description

      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.

      ./bin/standalone.sh -Djboss.socket.binding.port-offset=9

      /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

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17152 [GSS](7.2.z) jboss-cli.sh does not error on invalid options such as --controler

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: