Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1684

Uninformative error when using port 9999 for jboss-cli in alpha2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • 8.0.0.Alpha3
    • None
    • CLI
    • None

      Steps:

      1) Start wildfly alpha2
      2) Try to use jboss-cli.sh
      3) connect localhost:9999
      4) Server output reads:

      17:29:25,361 ERROR [org.jboss.remoting.remote.connection] (Remoting "rawbdor:MANAGEMENT" I/O-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856

      5) connect localhost:9990
      6) Success

      This seems strange, because actual management requests made via the management apis directly seem to go through without a problem and do not generate any 'invalid message length' errors in the console.

      This is causing a problem for tools. Tools needs to decide which management port to use. Unfortunately REMJMX does not work with 9990 yet.

      We could potentially work around this by doing management commands directly instead of issuing commands over ssh which get fed into jboss-cli, but, some users choose not to expose management port and so this method is actually relied upon by some users.

              darran.lofthouse@redhat.com Darran Lofthouse
              rob.stryker Rob Stryker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: