[jboss-jira] [JBoss JIRA] (WFLY-2490) Connecting using https-remoting times out and leaves thread within CLI spinning at 100%

[Darran Lofthouse (JIRA)]

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

Darran Lofthouse commented on WFLY-2490:
----------------------------------------

One additional piece of information, for the example where the thread is left spinning at 100% the CLI also does not contain any configuration to allow the servers certificate to be tested, we would expect this to result this in the user being prompted to decide if they want to trust the users certificate but in general this shows that the timeout and spinning is at a point where no connection to the server was established rather than a connection being established and the HTTP upgrade step failing.

                
> Connecting using https-remoting times out and leaves thread within CLI spinning at 100%
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-2490
>                 URL: https://issues.jboss.org/browse/WFLY-2490
>             Project: WildFly
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: CLI, Remoting
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>
> HTTP Upgrade is not fully working when SSL is enabled, other tasks will address that but this issue is about the CLI connecting to a server where HTTP Upgrade is not possible - a thread within the CLI is left running at 100% even after connecting has timed out.
> {noformat}
> [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
> {noformat}
> Connecting to the HTTP port where HTTP Upgrade is not available also results in a time out connecting rather than an early failure but does not result in the thread spinning at 100%
> {noformat}
> [disconnected /] connect http-remoting://localhost:9990
> The controller is not available at localhost:9990: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
> {noformat}

--
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