January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1684) Empty lines between tab completion suggestions on Windows

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1684?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-1684: -------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > Empty lines between tab completion suggestions on Windows > --------------------------------------------------------- > > Key: WFCORE-1684 > URL: https://issues.jboss.org/browse/WFCORE-1684 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Petr Kremensky > Assignee: Jean-Francois Denise > Priority: Minor > > I noticed that CLI put empty lines between lines with suggested values once the Windows terminal is set to maximal width. Issue appears *only of the CLI is connected to the EAP running in domain* mode. > *reproduce* > \- start EAP in domain mode > \- open a new terminal window, manually set the terminal width to maximal allowed value, but do not maximize the window > \- connect CLI to the running server and pres the Tab key > {noformat} > [domain@localhost:9990 /] > : clear data-source echo if pwd reload shutdown unset > alias command deploy echo-dmr jdbc-driver-info quit rollout-plan try version > batch connect deployment-info help ls read-attribute run-batch unalias xa-data-source > cd connection-info deployment-overlay history patch read-operation set undeploy > {noformat} > I was able to reproduce the issue on W2K8 and W2K12 servers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-432) CLI: Embedded Arrays need to be updatable easily

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-432?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-432: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > CLI: Embedded Arrays need to be updatable easily > ------------------------------------------------ > > Key: WFCORE-432 > URL: https://issues.jboss.org/browse/WFCORE-432 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jim Tyrrell > Assignee: Jean-Francois Denise > Labels: eap6-ux > > In the EAP 6 pilot we were presented a long string to create a Database Security Realm, it appears there is no way to update a single value. For example being able to change the string of the SQL of a principalsQuery or rolesQuery for example. Without having to put in the entire vale. > /profile=default/subsystem=security/security-domain=DB_domain:add(authentication=[{"code" => "Database", "flag" => "required", "module-options"=>[("principalsQuery"=>"Select password from UsersTable..... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-432) CLI: Embedded Arrays need to be updatable easily

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-432?page=com.atlassian.jira.plugin... ] Jean-Francois Denise closed WFCORE-432. --------------------------------------- Methods have been added in order to achieve this use case. Closing it. > CLI: Embedded Arrays need to be updatable easily > ------------------------------------------------ > > Key: WFCORE-432 > URL: https://issues.jboss.org/browse/WFCORE-432 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jim Tyrrell > Assignee: Jean-Francois Denise > Labels: eap6-ux > > In the EAP 6 pilot we were presented a long string to create a Database Security Realm, it appears there is no way to update a single value. For example being able to change the string of the SQL of a principalsQuery or rolesQuery for example. Without having to put in the entire vale. > /profile=default/subsystem=security/security-domain=DB_domain:add(authentication=[{"code" => "Database", "flag" => "required", "module-options"=>[("principalsQuery"=>"Select password from UsersTable..... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-430) CLI command to list/view AS modules

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-430?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-430: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > CLI command to list/view AS modules > ----------------------------------- > > Key: WFCORE-430 > URL: https://issues.jboss.org/browse/WFCORE-430 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Akram Ben Aissi > Assignee: Jean-Francois Denise > > For the same reason as AS7-4265, it would be useful to have command to list and view modules and their configuration. > For example: > modules list --name=org.jboss.* > or simply > modules list > will display a list of all available/installed modules in the AS. > The same way, > modules view --name=org.jboss.as.security --slot=name > will display details for the specified module, include its related resources and classes, and so on -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-428) cli - command to add/remove AS modules from non-default module root

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-428?page=com.atlassian.jira.plugin... ] Jean-Francois Denise resolved WFCORE-428. ----------------------------------------- Resolution: Duplicate It has been fixed by WFCORE-1626. > cli - command to add/remove AS modules from non-default module root > ------------------------------------------------------------------- > > Key: WFCORE-428 > URL: https://issues.jboss.org/browse/WFCORE-428 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Affects Versions: 1.0.0.Beta5 > Reporter: swapnesh sharma > Assignee: Joe Wertz > > cli - 'module add/remove' always adds/removes new module in %JOBSS_HOME%/modules directory. > It will be nice to allow add/remove from other default module root directory. Currently only search is allowed for this using JBOSS_MODULEPATH or -mp. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-409) Intermittent connection TimeOut with CLI using https-remoting

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-409?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-409: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > Intermittent connection TimeOut with CLI using https-remoting > ------------------------------------------------------------- > > Key: WFCORE-409 > URL: https://issues.jboss.org/browse/WFCORE-409 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Filip Bogyai > Assignee: Jean-Francois Denise > > When the management http-interface is secured to use https and the CLI is using https-remoting to connect, sometimes it hangs which leads to connection timeout. This occurs approximately in 1 out of 10 times if you try to connect with CLI in a short time. > {code} > org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9993 > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1028) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:840) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:819) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:276) > ... 8 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1005) > ... 11 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204) > at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:169) > at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:129) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 13 more > {code} > This problem also causes intermittent test failures in testsuite, for example: > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF&testNameI... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-418) Input/Output Formats Should Be Standard Formats (json/yaml/etc)

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-418?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-418: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > Input/Output Formats Should Be Standard Formats (json/yaml/etc) > --------------------------------------------------------------- > > Key: WFCORE-418 > URL: https://issues.jboss.org/browse/WFCORE-418 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Environment: RHEL 6.4, x86_64 > Reporter: Chris Pitman > Assignee: Jean-Francois Denise > Labels: automation, cli, configuration_management, json > > The purpose of the CLI is to improve automation for administrators, but the format used for data is a non-standard format that cannot be easily parsed or generated by any language. > The format is *really* close to json, but with enough deviation to make munging it a pain: replace hash rockets (=>) with colons, undefined with null, and key value pairs ("(a => b)") with hashes ("{a : b}"). Going in the opposite direction requires some sort of cleverness to determine what is a key-value pair, which is not fun. > The CLI should support both output and input in a standard format, so that the above hoops do not have to be jumped through. > Steps to Reproduce: > 1. Connect to the jboss cli > 2. Execute "/:whoami" > Actual results: > { > "outcome" => "success", > "result" => {"identity" => { > "username" => "$local", > "realm" => "ManagementRealm" > }}, > "response-headers" => {"process-state" => "reload-required"} > } > Expected results: > { > "outcome": "success", > "result": {"identity": { > "username": "$local", > "realm": "ManagementRealm" > }}, > "response-headers": {"process-state": "reload-required"} > } -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-426) Auto more/less in CLI for multi-page output

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-426?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-426: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > Auto more/less in CLI for multi-page output > ------------------------------------------- > > Key: WFCORE-426 > URL: https://issues.jboss.org/browse/WFCORE-426 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Darran Lofthouse > Assignee: Jean-Francois Denise > > Where the result of a management operation in the CLI returns multiple screens of output it would be nice if this could be automatically wrapped in a more/less type behaviour. > Similar to how git handles git log compared to how svn handles svn log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-431) CLI should WARN about usage deprecated api

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-431?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-431: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > CLI should WARN about usage deprecated api > ------------------------------------------ > > Key: WFCORE-431 > URL: https://issues.jboss.org/browse/WFCORE-431 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Tomaz Cerar > Assignee: Jean-Francois Denise > > We added support for deprecating resources/attributes/operations/parameters some time ago. > I would be a good thing that we would warn users if they are using deprecated API. > Every resource/attribute/operation/param that is deprecated has extra element "deprecated" in metadata > With sub elements > - "since", which tells in what version it was deprecated > - "reason", text description why it is deprecated. > Reason in most cases also tells what is new replacement. > This should be only displayed in case of interactive shell usage. > Unless there is also some special CLI log file, it could be part of that even for non-interactive usage -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-427) CLI doesn't read alias from .jbossclirc

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-427?page=com.atlassian.jira.plugin... ] Jean-Francois Denise reassigned WFCORE-427: ------------------------------------------- Assignee: Jean-Francois Denise (was: Alexey Loubyansky) > CLI doesn't read alias from .jbossclirc > --------------------------------------- > > Key: WFCORE-427 > URL: https://issues.jboss.org/browse/WFCORE-427 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Osamu Nagano > Assignee: Jean-Francois Denise > > By WFLY-1063, a variable can be defined in .jbossclirc and preloaded by CLI. But aliases are not able to define with {{org.jboss.as.cli.CliInitializationException}}. > {code} > $ cat .jbossclirc > set prod_db=/subsystem=datasources/data-source=ExampleDS > alias ll=ls -l > $ $JBOSS_HOME/bin/jboss-cli.sh -c > Unexpected command 'alias ll=ls -l'. Type 'help --commands' for the list of supported commands. > org.jboss.as.cli.CliInitializationException: Failed to process /home/onagano/cases/01180422/wf810/.jbossclirc > at org.jboss.as.cli.impl.CliLauncher.runcom(CliLauncher.java:352) > at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:305) > at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > {code} > Enclosing by single quote or double quote won't help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2017