[jboss-jira] [JBoss JIRA] (WFLY-7001) CLI 'deployment-info --headers' throws errors in standalone mode
Bartosz Baranowski (JIRA)
issues at jboss.org
Thu Aug 25 07:11:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-7001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bartosz Baranowski updated WFLY-7001:
-------------------------------------
Description:
In standalone mode of jboss-cli, the command: 'deployment-info --headers' throws Java exceptions instead of a proper problem description.
{code:bash}
[standalone at localhost:9990 /] deployment-info --headers
Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null
{code}
Tab complete does not work beyond '--headers=' and starts working again after '\{' is typed.
*Example*:
{code:bash}
[standalone at localhost:9990 /] deployment-info --headers<TAB>=<TAB><TAB>
Failed to handle 'deployment-info --headers=': newValue is null
[standalone at localhost:9990 /] deployment-info --headers={<TAB>
allow-resource-service-restart rollback-on-runtime-failure
blocking-timeout rollout
{code}
*Steps to reproduce*:
Standalone:
{code:bash}
[standalone at localhost:9990 /] deployment-info --headers
Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null
[standalone at localhost:9990 /] deployment-info --headers=<TAB><TAB>
Failed to handle 'deployment-info --headers=': newValue is null
[standalone at localhost:9990 /] deployment-info --headers={}
NAME RUNTIME-NAME PERSISTENT ENABLED STATUS
jboss-kitchensink-ml-ear.ear jboss-kitchensink-ml-ear.ear true false STOPPED
jboss-kitchensink.war jboss-kitchensink.war true false STOPPED
jboss-modules.jar jboss-modules.jar true false STOPPED
{code}
> CLI 'deployment-info --headers' throws errors in standalone mode
> ----------------------------------------------------------------
>
> Key: WFLY-7001
> URL: https://issues.jboss.org/browse/WFLY-7001
> Project: WildFly
> Issue Type: Bug
> Reporter: Bartosz Baranowski
> Assignee: Jason Greene
>
> In standalone mode of jboss-cli, the command: 'deployment-info --headers' throws Java exceptions instead of a proper problem description.
> {code:bash}
> [standalone at localhost:9990 /] deployment-info --headers
> Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null
> {code}
> Tab complete does not work beyond '--headers=' and starts working again after '\{' is typed.
> *Example*:
> {code:bash}
> [standalone at localhost:9990 /] deployment-info --headers<TAB>=<TAB><TAB>
> Failed to handle 'deployment-info --headers=': newValue is null
> [standalone at localhost:9990 /] deployment-info --headers={<TAB>
> allow-resource-service-restart rollback-on-runtime-failure
> blocking-timeout rollout
> {code}
> *Steps to reproduce*:
> Standalone:
> {code:bash}
> [standalone at localhost:9990 /] deployment-info --headers
> Failed to perform operation: java.util.concurrent.ExecutionException: Operation failed: Operation failed: java.lang.IllegalArgumentException:null
> [standalone at localhost:9990 /] deployment-info --headers=<TAB><TAB>
> Failed to handle 'deployment-info --headers=': newValue is null
> [standalone at localhost:9990 /] deployment-info --headers={}
> NAME RUNTIME-NAME PERSISTENT ENABLED STATUS
> jboss-kitchensink-ml-ear.ear jboss-kitchensink-ml-ear.ear true false STOPPED
> jboss-kitchensink.war jboss-kitchensink.war true false STOPPED
> jboss-modules.jar jboss-modules.jar true false STOPPED
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list