[jboss-jira] [JBoss JIRA] (WFCORE-3667) Wildfly 12 : jboss-cli.sh in infinite loop
Gaétan QUENTIN (JIRA)
issues at jboss.org
Tue Mar 6 16:07:00 EST 2018
[ https://issues.jboss.org/browse/WFCORE-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542376#comment-13542376 ]
Gaétan QUENTIN commented on WFCORE-3667:
----------------------------------------
same results.
attached log file.
[^jboss-cli.log]
> Wildfly 12 : jboss-cli.sh in infinite loop
> -------------------------------------------
>
> Key: WFCORE-3667
> URL: https://issues.jboss.org/browse/WFCORE-3667
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Environment: ubuntu 16.06 lxd container
> java version "1.8.0_161" oracle
> v12 migrated from v11
> Reporter: Gaétan QUENTIN
> Assignee: Jean-Francois Denise
> Priority: Critical
> Labels: regression
> Attachments: aesh-readline-1.5.jar, jboss-cli-logging.properties, jboss-cli.25300, term.txt
>
>
> i cannot use anymore the jboss-cli.sh to connect to the contoller since i migrated from v11 to with wildfly 12:
>
> wildfly at java2:/opt/Wildfly$ ls -la
> drwxr-xr-x 1 root root 156 Mar 3 20:36 jboss-server-migration
> drwxr-xr-x 1 root root 454 Mar 4 00:09 overlays
> drwxr-xr-x 1 root root 166 Mar 4 11:43 scripts
> drwxr-xr-x 1 root root 236 Oct 24 05:30 wildfly-11.0.0.Final
> drwxr-xr-x 1 root root 236 Mar 1 07:29 wildfly-12.0.0.Final
> lrwxrwxrwx 1 root root 20 Mar 4 12:49 wildfly-current -> wildfly-12.0.0.Final
>
>
> my wildfly management console is on 172.20.12.192.
> v12 has been migrated from v11 with the jboss-server-migration tool. Applications and app manager works fine and the wildfly instance controller is well binded on the requested ip.
>
>
> with wildfly-current link on -> wildfly-11.0.0.Final:
>
> this works perfectly:
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
>
> with wildfly-current -> wildfly-12.0.0.Final:
> this go in infinite loop until crash :
> (cd /opt/Wildfly/wildfly-current/bin && ./jboss-cli.sh -c -u=xx -p=xx --controller=http-remoting://172.20.12.192:9990)
>
> output:
>
> '[standalone at 172.20.12.192:9990' is not a valid operation name.
> [standalone at 172.20.12.192:9990 /] '[standalone at 172.20.12.192:9990' is not a valid operation name.
> ''[standalone at 172.20.12.192:9990'' is not a valid operation name.
> [standalone at 172.20.12.192:9990 /] [standalone at 172.20.12.192:9990 /] ''[standalone at 172.20.12.192:9990'' is not a valid operation name.
> '[standalone at 172.20.12.192:9990' is not a valid operation name.
> [standalone at 172.20.12.192:9990 /] '''[standalone at 172.20.12.192:9990''' is not a valid operation name.
> ''''[standalone at 172.20.12.192:9990'''' is not a valid operation name.
> [standalone at 172.20.12.192:9990 /] [standalone at 172.20.12.192:9990 /] [standalone at 172.20.12.192:9990 /] [standalone at 172.20.12.192:9990 /] ''[standalone at 172.20.12.192:9990'' is not a valid oper is not a valid operation name.
> '[standalone at 172.20.12.192:9990' is not a valid operation name.
> [standalone at 172.20.12.192:9990 /] '''''[standalone at 172.20.12.192:9990''''' is not a valid operation name.
> ''''''[standalone at 172.20.12.192:9990'''''' is not a valid operation name.
> attached is a strace capture file (one of thousands) of jboss-cli .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list