[jboss-jira] [JBoss JIRA] (WFLY-9949) Wildfly 12 : jboss-cli.sh in infinite loop

Gaétan QUENTIN (JIRA) issues at jboss.org
Sun Mar 4 11:12:00 EST 2018


Gaétan QUENTIN created WFLY-9949:
------------------------------------

             Summary: Wildfly 12 : jboss-cli.sh in infinite loop 
                 Key: WFLY-9949
                 URL: https://issues.jboss.org/browse/WFLY-9949
             Project: WildFly
          Issue Type: Bug
          Components: CLI
    Affects Versions: 12.0.0.Final
         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
         Attachments: jboss-cli.25300

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