[jboss-jira] [JBoss JIRA] (WFLY-2207) CLI Unable to connect using https-remoting address.

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809186#comment-12809186 ] 

Darran Lofthouse commented on WFLY-2207:
----------------------------------------

With TRACE logging enabled the CLI appears to be stuck in an infinate loop for 5 seconds repeating the following each time: -

{code}
14:41:37,014 TRACE [org.xnio.nio.selector] Beginning select on sun.nio.ch.EPollSelectorImpl at 474906b9
14:41:37,015 TRACE [org.xnio.nio.selector] Selected on sun.nio.ch.EPollSelectorImpl at 474906b9
14:41:37,015 TRACE [org.xnio.nio.selector] Selected key sun.nio.ch.SelectionKeyImpl at 187feca0 for java.nio.channels.SocketChannel[connected local=/127.0.0.1:50836 remote=localhost/127.0.0.1:9993]
14:41:37,015 TRACE [org.xnio.listener] Invoking listener org.xnio.http.HttpUpgrade$HttpUpgradeState$UpgradeResultListener at 20a12d8f on channel org.xnio.conduits.ConduitStreamSourceChannel at 35b61805
{code}
                
> CLI Unable to connect using https-remoting address.
> ---------------------------------------------------
>
>                 Key: WFLY-2207
>                 URL: https://issues.jboss.org/browse/WFLY-2207
>             Project: WildFly
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>            Priority: Critical
>             Fix For: 8.0.0.Beta1
>
>
> 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