Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10372

http-interface.http-upgrade should not be marked as "restart-required" => "no-services"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR17
    • 7.1.0.DR16
    • Management
    • None

      Although http-upgrade attribute is marked as "restart-required" => "no-services" in model, when I try change it, server gets into reload required state, anyway.

      [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) 
      {
          "outcome" => "success",
          "response-headers" => {
              "operation-requires-reload" => true,
              "process-state" => "reload-required"
          }
      }
      

      This issue foolows-up JBEAP-9137, where all other http-interface where marked as "restart-required" => "all-services". So seems to me http-upgrade was ommited just by mistake.

          "http-upgrade" => {
              "type" => OBJECT,
              "description" => "HTTP Upgrade specific configuration",
              "expressions-allowed" => false,
              "required" => false,
              "nillable" => true,
              "value-type" => {
                  "enabled" => {
                      "type" => BOOLEAN,
                      "description" => "Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections",
                      "expressions-allowed" => false,
                      "required" => false,
                      "nillable" => true,
                      "default" => false
                  },
                  "sasl-authentication-factory" => {
                      "type" => STRING,
                      "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
                      "expressions-allowed" => false,
                      "required" => false,
                      "nillable" => true,
                      "capability-reference" => "org.wildfly.security.sasl-authentication-factory",
                      "min-length" => 1L,
                      "max-length" => 2147483647L
                  }
              },
              "access-type" => "read-write",
              "storage" => "configuration",
              "restart-required" => "no-services"
          }
      

      Upstream: https://github.com/wildfly/wildfly-core/pull/2347

              kwills@redhat.com Ken Wills
              mchoma@redhat.com Martin Choma
              Martin Choma Martin Choma
              Martin Choma Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: