[JBoss JIRA] (WFLY-2207) CLI Unable to connect using https-remoting address.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-2207?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-2207:
-----------------------------------
Parent: WFLY-1597
Issue Type: Sub-task (was: Bug)
> CLI Unable to connect using https-remoting address.
> ---------------------------------------------------
>
> Key: WFLY-2207
> URL: https://issues.jboss.org/browse/WFLY-2207
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: CLI
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.CR1
>
>
> The CLI is failing to connect over https with the following: -
> {code}
> [disconnected /] connect https-remoting://localhost:9993
> The controller is not available at localhost:9993: java.net.ConnectException: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out: JBAS012144: Could not connect to https-remoting://localhost:9993. The connection timed out
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2154) http-interface is used instead of native-interface for native access
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-2154?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-2154:
-----------------------------------
Parent: WFLY-1597
Issue Type: Sub-task (was: Bug)
> http-interface is used instead of native-interface for native access
> --------------------------------------------------------------------
>
> Key: WFLY-2154
> URL: https://issues.jboss.org/browse/WFLY-2154
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Domain Management, Security
> Affects Versions: 8.0.0.Beta1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> Steps to reproduce:
> 1) create new Security Realm in standalone.xml:
> <security-realm name="ManagementTestRealm">
> <authentication>
> <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
> </authentication>
> </security-realm>
> 2) make http-interface using this realm:
> <http-interface security-realm="ManagementTestRealm" http-upgrade-enabled="true">
> <socket-binding http="management-http"/>
> </http-interface>
> 3) start standalone server
> 4) run CLI with command ./jboss-cli.sh -c
> You will ask for user and password for ManagementTestRealm but this realm is NOT used for native interface! It should still used ManagementRealm not ManagementTestRealm. If you add <local default-user="$local"/> to ManagementTestRealm Security Realm and run CLI again, it connect successfully. It looks like there is used http-interface instead of native-interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-2211) NullPointerException in RemotingHttpUpgradeService if no http port.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-2211?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-2211:
-----------------------------------
Parent: WFLY-1597
Issue Type: Sub-task (was: Bug)
> NullPointerException in RemotingHttpUpgradeService if no http port.
> -------------------------------------------------------------------
>
> Key: WFLY-2211
> URL: https://issues.jboss.org/browse/WFLY-2211
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 8.0.0.CR1
>
>
> Starting with a HTTP port is not mandatory.
> {code}
> Caused by: java.lang.NullPointerException
> at org.jboss.as.remoting.RemotingHttpUpgradeService.start(RemotingHttpUpgradeService.java:107) [wildfly-remoting-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-1664) bin]$ ./jboss-cli.sh -c --controller=localhost:9999 - Results in Connection Timed Out
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1664?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-1664:
-----------------------------------
Parent: WFLY-1597
Workaround Description: (was: Add the URI scheme to the controller paramter: -
{code}
./jboss-cli.sh -c --controller=remote://localhost:9999
{code})
Issue Type: Sub-task (was: Bug)
Workaround: (was: Workaround Exists)
> bin]$ ./jboss-cli.sh -c --controller=localhost:9999 - Results in Connection Timed Out
> -------------------------------------------------------------------------------------
>
> Key: WFLY-1664
> URL: https://issues.jboss.org/browse/WFLY-1664
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: CLI
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> Port 9999 is by default the native management interface.
> The command './jboss-cli.sh -c --controller=localhost:9999' results in the following error: -
> {code}
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:291)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:269)
> 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:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:411)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:967)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:806)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:778)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:289)
> ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost: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:945)
> ... 11 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> 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:162)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:124)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)
> 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 is because the use of HTTP upgrade is assumed, however clients using the CLI from previous versions were used to using this connection command against the native management interface only.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (WFLY-1664) bin]$ ./jboss-cli.sh -c --controller=localhost:9999 - Results in Connection Timed Out
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-1664?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-1664:
-----------------------------------
Description:
Port 9999 is by default the native management interface.
The command './jboss-cli.sh -c --controller=localhost:9999' results in the following error: -
{code}
org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:291)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:269)
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:601)
at org.jboss.modules.Module.run(Module.java:270)
at org.jboss.modules.Main.main(Main.java:411)
Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:967)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:806)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:778)
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:289)
... 8 more
Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost: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:945)
... 11 more
Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9999. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
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:162)
at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:124)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)
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 is because the use of HTTP upgrade is assumed, however clients using the CLI from previous versions were used to using this connection command against the native management interface only.
Workaround: -
Add the URI scheme to the controller paramter: -
{code}
./jboss-cli.sh -c --controller=remote://localhost:9999
{code}
was:
Port 9999 is by default the native management interface.
The command './jboss-cli.sh -c --controller=localhost:9999' results in the following error: -
{code}
org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:291)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:269)
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:601)
at org.jboss.modules.Module.run(Module.java:270)
at org.jboss.modules.Main.main(Main.java:411)
Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:967)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:806)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:778)
at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:289)
... 8 more
Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost: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:945)
... 11 more
Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9999. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
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:162)
at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:124)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)
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 is because the use of HTTP upgrade is assumed, however clients using the CLI from previous versions were used to using this connection command against the native management interface only.
> bin]$ ./jboss-cli.sh -c --controller=localhost:9999 - Results in Connection Timed Out
> -------------------------------------------------------------------------------------
>
> Key: WFLY-1664
> URL: https://issues.jboss.org/browse/WFLY-1664
> Project: WildFly
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: CLI
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> Port 9999 is by default the native management interface.
> The command './jboss-cli.sh -c --controller=localhost:9999' results in the following error: -
> {code}
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:291)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:269)
> 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:601)
> at org.jboss.modules.Module.run(Module.java:270)
> at org.jboss.modules.Main.main(Main.java:411)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9999
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:967)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:806)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:778)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:289)
> ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost: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:945)
> ... 11 more
> Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> 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:162)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:124)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90)
> 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 is because the use of HTTP upgrade is assumed, however clients using the CLI from previous versions were used to using this connection command against the native management interface only.
> Workaround: -
> Add the URI scheme to the controller paramter: -
> {code}
> ./jboss-cli.sh -c --controller=remote://localhost:9999
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months