[JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh
by André Caldeira (JIRA)
[ https://issues.jboss.org/browse/WFLY-4288?page=com.atlassian.jira.plugin.... ]
André Caldeira commented on WFLY-4288:
--------------------------------------
Hi,
we are using eap6.4.11 and problem still happens... but this is eap so please close the case.
thanks
> 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: Alexey Loubyansky
>
> 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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-4288?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise commented on WFLY-4288:
--------------------------------------------
Hi, any update on this one? Did you update to more recent version? It seems reasonable to close this bug.
> 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: Alexey Loubyansky
>
> 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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ELY-862) Elytron dir-context supports only plaintext password
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-862?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina moved WFLY-7855 to ELY-862:
--------------------------------------
Project: WildFly Elytron (was: WildFly)
Key: ELY-862 (was: WFLY-7855)
Component/s: Realms
(was: Security)
Affects Version/s: (was: 11.0.0.Alpha1)
> Elytron dir-context supports only plaintext password
> ----------------------------------------------------
>
> Key: ELY-862
> URL: https://issues.jboss.org/browse/ELY-862
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Realms
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Blocker
>
> Only plaintext password is currently able to be configured in Elytron dir-context resource. Any integration with Credential store is missing.
> We request blocker since it seems that there is currently no option how to provide non-plaintext password for dir-context to server configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7855) Elytron dir-context supports only plaintext password
by Jan Kalina (JIRA)
Jan Kalina created WFLY-7855:
--------------------------------
Summary: Elytron dir-context supports only plaintext password
Key: WFLY-7855
URL: https://issues.jboss.org/browse/WFLY-7855
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Blocker
Only plaintext password is currently able to be configured in Elytron dir-context resource. Any integration with Credential store is missing.
We request blocker since it seems that there is currently no option how to provide non-plaintext password for dir-context to server configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7820) Add AuthenticationContext References to Undertow
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7820?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse resolved WFLY-7820.
------------------------------------
Resolution: Rejected
Instead of the Undertow subsystem referencing the AuthenticationContext the Elytron subsystem now contains a pair of DeploymentUnitProcessors which depend on a default AuthenticationContext and associate it with all deployments.
> Add AuthenticationContext References to Undertow
> ------------------------------------------------
>
> Key: WFLY-7820
> URL: https://issues.jboss.org/browse/WFLY-7820
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> These references will be associated with the ClassLoader of the deployment so will be available for any outbound connections from the deployment.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2154) Enhance CLI logging
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2154?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-2154:
--------------------------------------------
Assignee: Jean-Francois Denise
> Enhance CLI logging
> -------------------
>
> Key: WFCORE-2154
> URL: https://issues.jboss.org/browse/WFCORE-2154
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
>
> When debugging complex use cases, the current level of CLI logging is weak. Furthermore aesh 0.66.x does handle logs in a custom way that can't be enabled from cli logging config file.
> I plan to fix that once we are have aesh-readline in.
> - aesh-readline logging is pure JUL, so can be enabled from CLI
> - CLI config file will be updated to have aesh logger enabled.
> - New traces will be added to CLI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2154) Enhance CLI logging
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2154:
--------------------------------------------
Summary: Enhance CLI logging
Key: WFCORE-2154
URL: https://issues.jboss.org/browse/WFCORE-2154
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Jean-Francois Denise
When debugging complex use cases, the current level of CLI logging is weak. Furthermore aesh 0.66.x does handle logs in a custom way that can't be enabled from cli logging config file.
I plan to fix that once we are have aesh-readline in.
- aesh-readline logging is pure JUL, so can be enabled from CLI
- CLI config file will be updated to have aesh logger enabled.
- New traces will be added to CLI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months