December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-419) Expose client socket binding config through CLI connect configs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-419?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-211 to WFCORE-419: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-419 (was: WFLY-211) Component/s: CLI (was: CLI) Fix Version/s: 1.0.0.Beta1 (was: 9.0.0.Beta1) > Expose client socket binding config through CLI connect configs > --------------------------------------------------------------- > > Key: WFCORE-419 > URL: https://issues.jboss.org/browse/WFCORE-419 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 1.0.0.Beta1 > > > Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-420) Escape to shell

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-420?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-728 to WFCORE-420: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-420 (was: WFLY-728) Component/s: CLI (was: CLI) Fix Version/s: (was: No Release) > Escape to shell > --------------- > > Key: WFCORE-420 > URL: https://issues.jboss.org/browse/WFCORE-420 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Environment: all > Reporter: Rich Sharples > Assignee: Alexey Loubyansky > Priority: Minor > > It would be really useful to be able to escape to an (OS) shell from the CLI - most Linux commands / shells allow you to do this with eg. "!". -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-414) Issue in Interactive mode on cygwin not working.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-414?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-908 to WFCORE-414: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-414 (was: WFLY-908) Affects Version/s: (was: 8.0.0.CR1) Component/s: CLI (was: CLI) > Issue in Interactive mode on cygwin not working. > ------------------------------------------------ > > Key: WFCORE-414 > URL: https://issues.jboss.org/browse/WFCORE-414 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: Windows 7, windows2k8, Cygwin 1.7.15 > Reporter: Peter Cadman > Assignee: Alexey Loubyansky > Priority: Minor > > After connecting to standalone server on localhost, Cgywin doesn't response to input. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-415) Pressing up-arrow crashed CLI on windows

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-415?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1799 to WFCORE-415: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-415 (was: WFLY-1799) Affects Version/s: (was: 8.0.0.Alpha4) Component/s: CLI (was: CLI) > Pressing up-arrow crashed CLI on windows > ---------------------------------------- > > Key: WFCORE-415 > URL: https://issues.jboss.org/browse/WFCORE-415 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Nicklas Karlsson > Assignee: Alexey Loubyansky > > Pressing the up-arrow in the CLI on windows crashes it with > {code} > [standalone@localhost:9990 /] java.lang.NumberFormatException: For input string: > "1B" > at java.lang.NumberFormatException.forInputString(NumberFormatException. > java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.<init>(Integer.java:677) > at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120 > ) > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.PrintWriter.flush(PrintWriter.java:320) > at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal > .java:88) > at org.jboss.aesh.console.Console.drawLine(Console.java:1011) > at org.jboss.aesh.console.Console.redrawLine(Console.java:990) > at org.jboss.aesh.console.Console.getHistoryElement(Console.java:753) > at org.jboss.aesh.console.Console.parseOperation(Console.java:556) > at org.jboss.aesh.console.Console.read(Console.java:446) > at org.jboss.aesh.console.Console.read(Console.java:346) > at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:177) > at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl. > java:1198) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:270) > 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(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:411) > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-416) Inconsistent tab completion behaviour between commands and arguments

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-416?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-932 to WFCORE-416: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-416 (was: WFLY-932) Component/s: CLI (was: CLI) > Inconsistent tab completion behaviour between commands and arguments > -------------------------------------------------------------------- > > Key: WFCORE-416 > URL: https://issues.jboss.org/browse/WFCORE-416 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Minor > > When tab is used for completion, the behavior changes when there is only 1 remaining candidate. > For commands, when the completion leads to a single candidate, a whitespace is appended and we can proceed to the arguments > For arguments using a TabCompleter, when the completion leads to a single candidate, no whitespace is appended and we have to type it to be able to proceed to the next argument > > Example: > * deployment-over<TAB> > => will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace is appended to the single candidate) > * deployment-overlay a<TAB> > => will complete to deployment-overlay add<CURSOR> (no whitespace appended even though add is the only candidate matched) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-412) Pressing the tab key whilst entering a username for authentication deadlocks the CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-412?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3476 to WFCORE-412: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-412 (was: WFLY-3476) Affects Version/s: (was: 8.1.0.Final) Component/s: CLI (was: CLI) > Pressing the tab key whilst entering a username for authentication deadlocks the CLI > ------------------------------------------------------------------------------------ > > Key: WFCORE-412 > URL: https://issues.jboss.org/browse/WFCORE-412 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Darran Lofthouse > Assignee: Alexey Loubyansky > Attachments: cli_deadlock.txt > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-413) [cli] exit against remote server fails

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-413?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1591 to WFCORE-413: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-413 (was: WFLY-1591) Affects Version/s: (was: 8.0.0.Alpha2) Component/s: CLI (was: CLI) > [cli] exit against remote server fails > -------------------------------------- > > Key: WFCORE-413 > URL: https://issues.jboss.org/browse/WFCORE-413 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Rob Stryker > Assignee: Alexey Loubyansky > Attachments: WFLY-1591.stack.txt > > > Using ./jboss-cli.sh from a local wildfly alpha2 against a remote wildfly alpha2 connects and functions properly. A call to exit freezes entirely. > jstack to be attached -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-409?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3311 to WFCORE-409: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-409 (was: WFLY-3311) Affects Version/s: (was: 8.1.0.CR1) Component/s: CLI (was: CLI) > 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: Alexey Loubyansky > > 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 (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-410) alias --help print nothing on jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-410?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1628 to WFCORE-410: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-410 (was: WFLY-1628) Affects Version/s: (was: 8.0.0.Alpha2) Component/s: CLI (was: CLI) > alias --help print nothing on jboss-cli > --------------------------------------- > > Key: WFCORE-410 > URL: https://issues.jboss.org/browse/WFCORE-410 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: MacOS X, JDK 1.7.0_09 > Reporter: Alexis Hassler > Assignee: Alexey Loubyansky > > I have no output when I call this : > [standalone@localhost:9990 /] alias --help > [standalone@localhost:9990 /] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3454 to WFCORE-411: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-411 (was: WFLY-3454) Component/s: CLI Patching (was: CLI) (was: Patching) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Emanuel Muckenhuber > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 December 2014