[jboss-jira] [JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh

Brian Stansberry (JIRA) issues at jboss.org
Wed Nov 4 22:41:00 EST 2015


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

Brian Stansberry updated WFLY-4288:
-----------------------------------
    Component/s: CLI


> error when trying to execute commands using jboss-cli.sh
> --------------------------------------------------------
>
>                 Key: WFLY-4288
>                 URL: https://issues.jboss.org/browse/WFLY-4288
>             Project: WildFly
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: JBoss AS7 7.2.0.Final
>            Reporter: André Caldeira
>            Assignee: Jason Greene
>
> Hi,
> I've configured jboss to use ssl, and after this change, sometimes, the command cannot be executed:
> [root@<node> ~]# /opt/oss/NSN-SQM-sqm_jboss/install/jboss-eap-6.2/bin/jboss-cli.sh --connect
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
>         at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:284)
>         at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:262)
>         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:292)
>         at org.jboss.modules.Main.main(Main.java:455)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
>         at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:969)
>         at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:808)
>         at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:784)
>         at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:282)
>         ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
>         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:947)
>         ... 11 more
> Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
>         at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129)
>         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:160)
>         at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:120)
>         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
> Caused by: java.net.ConnectException: Connection refused
>         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
>         at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:322)
>         at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:318)
>         at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
>         at org.xnio.nio.NioHandle.run(NioHandle.java:90)
>         at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
>         at ...asynchronous invocation...(Unknown Source)
>         at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
>         at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
>         at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
>         at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
>         at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80)
>         at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99)
>         ... 23 more
> In server.log what I can see when it happens is:
> 17:08:30,279 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:08:42,071 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:11:47,100 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> this problem only happens sometimes...
> Thanks in advance,
> Br,
> André



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



More information about the jboss-jira mailing list