[jboss-jira] [JBoss JIRA] (WFCORE-4560) HTTP management interface fails to start if backed by a "https" socket-binding

[Richard Opalka (Jira)]

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

Richard Opalka commented on WFCORE-4560:
----------------------------------------

Thanks [~jaikiran]. [~jmesnil] this behaviour was intentional but backward compatibility has precedence. 
I created https://issues.jboss.org/browse/MSC-247 to fix this.

> HTTP management interface fails to start if backed by a "https" socket-binding
> ------------------------------------------------------------------------------
>
>                 Key: WFCORE-4560
>                 URL: https://issues.jboss.org/browse/WFCORE-4560
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 9.0.2.Final, 10.0.0.Beta1
>            Reporter: Jaikiran Pai
>            Assignee: Jeff Mesnil
>            Priority: Major
>             Fix For: 10.0.0.Beta2
>
>
> A user has reported that WildFly 17.0.0.Final fails to start when ManagementRealm is backed by a socket-binding which uses HTTPS. More details about this issue are here https://developer.jboss.org/thread/280311.
> There's actually more than one issue in that thread:
> 1. The failure to start
> 2. The absence of any error message indicating what failed.
> This JIRA is mainly to track the failure to start and a separate JIRA can/will probably be opened for dealing with the absence of the error message (since I am guessing that it's going to be a more generic issue/change).



--
This message was sent by Atlassian Jira
(v7.12.1#712002)