Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4560

HTTP management interface fails to start if backed by a "https" socket-binding

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 10.0.0.Beta2, 10.0.0.Final
    • 9.0.2.Final, 10.0.0.Beta1
    • Server
    • None

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

            jmesnil1@redhat.com Jeff Mesnil
            jaikiran Jaikiran Pai (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: