[jboss-jira] [JBoss JIRA] (WFCORE-1767) Exception on tab completion when adding new JGroups stack

[Alexey Loubyansky (JIRA)]

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

Alexey Loubyansky moved JBEAP-5881 to WFCORE-1767:
--------------------------------------------------

              Project: WildFly Core  (was: JBoss Enterprise Application Platform)
                  Key: WFCORE-1767  (was: JBEAP-5881)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: CLI
                           (was: CLI)
    Affects Version/s:     (was: 7.1.0.DR3)


> Exception on tab completion when adding new JGroups stack
> ---------------------------------------------------------
>
>                 Key: WFCORE-1767
>                 URL: https://issues.jboss.org/browse/WFCORE-1767
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Alexey Loubyansky
>            Assignee: Alexey Loubyansky
>
> I just happened to catch the following exception:
> {noformat}
> Exception in thread "Aesh Process Loop 1360657223" java.lang.IllegalArgumentException
> 	at org.jboss.dmr.ModelValue.asType(ModelValue.java:147)
> 	at org.jboss.dmr.ModelNode.asType(ModelNode.java:321)
> 	at org.jboss.as.cli.impl.ValueTypeCompleter$ComplexInstance.isCompliantType(ValueTypeCompleter.java:236)
> 	at org.jboss.as.cli.impl.ValueTypeCompleter$Instance.getType(ValueTypeCompleter.java:100)
> 	at org.jboss.as.cli.impl.ValueTypeCompleter$ValueTypeCallbackHandler.getCandidates(ValueTypeCompleter.java:414)
> 	at org.jboss.as.cli.impl.ValueTypeCompleter.complete(ValueTypeCompleter.java:323)
> 	at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:254)
> 	at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:74)
> 	at org.jboss.as.cli.CommandCompleter.doComplete(CommandCompleter.java:134)
> 	at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:63)
> 	at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:143)
> 	at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:150)
> 	at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:420)
> 	at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:165)
> 	at org.jboss.aesh.console.Console.processInternalOperation(Console.java:767)
> 	at org.jboss.aesh.console.Console.execute(Console.java:727)
> 	at org.jboss.aesh.console.Console.access$900(Console.java:73)
> 	at org.jboss.aesh.console.Console$6.run(Console.java:636)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> {noformat}
> when double tapping tab on the following:
> {noformat}
> [standalone at localhost:9990 /] /subsystem=jgroups/stack=anothertcp:add(transport={type=TCP,socket-binding=jgroups-tcp},protocols=[{
> {noformat}
> When trying a second time, it popped up again, so it is likely reproducible. Note that EAP was started with:
> {code}
> ./standalone -c standalone-ha.xml
> {code}
> and the EAP was in a different directory than the {{jboss-cli.sh}}, though I don't think that should matter.
> * EAP: $MYDIR/jboss-eap-7.1.0.DR3-playground/bin/standalone.sh
> * jboss-cli: $MYDIR/jboss-eap-7.1.0.DR3-clean/bin/jboss-cli.sh
> The exception killed the CLI.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)