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

Details

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

    Description

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

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. MSC-247 Allow also provided not just aliased services to be accessible

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: