JBoss Community

Using the CLI remote client jar

new comment by Miguel Reyes View all comments on this document

jboss-cli-client.jar works fine in Fedora. However, when I try to run it in Win7 I get a "connection timeout" error:

 

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

 

C:\Users\myuser\Desktop\Test>java -jar jboss-cli-client.jar --controller=10.11.12.13:9999 --connect --user=admin --password=admin --file=test.cli

WARN: can't find jboss-cli.xml. Using default configuration values.

apr 09, 2013 10:35:21 FM org.xnio.Xnio <clinit>

INFO: XNIO Version 3.0.7.GA

apr 09, 2013 10:35:21 FM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.0.7.GA

apr 09, 2013 10:35:21 FM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version 3.2.14.GA

org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

        at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:280)

        at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:240)

        at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)

Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 10.11.12.13:9999

        at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:950)

        at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:789)

        at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:765)

        at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:278)

        ... 2 more

Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could notconnect to remote://10.11.12.13:9999. 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:928)

        ... 5 more

Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://10.11.12.13:9999. The connection timed out

        at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:130)

        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:176)

        at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:153)

        at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:114)

        at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)

        at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)

        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)

        ... 7 more

 

My workaround right now is to pass the connect command in my test.cli (connect 10.11.12.13) and instead run:

 

C:\Users\myuser\Desktop\Test>java -jar jboss-cli-client.jar --user=admin --password=admin --file=test.cli

 

Still, I would like to be able to pass the server IP as part of the execution line so that I can run the same test.cli file against several servers...

 

Using the jboss-cli-client.jar from EAP6.1.ALPHA