[jboss-jira] [JBoss JIRA] (WFLY-1684) Uninformative error when using port 9999 for jboss-cli in alpha2

[Darran Lofthouse (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darran Lofthouse reassigned WFLY-1684:
--------------------------------------

    Assignee: Darran Lofthouse  (was: Alexey Loubyansky)

    
> Uninformative error when using port 9999 for jboss-cli in alpha2
> ----------------------------------------------------------------
>
>                 Key: WFLY-1684
>                 URL: https://issues.jboss.org/browse/WFLY-1684
>             Project: WildFly
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Rob Stryker
>            Assignee: Darran Lofthouse
>
> 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. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira