Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14396

WildFly does not start when async-registration attribute in XTS subsystem is set to an expression

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 22.0.0.Final
    • XTS
    • None
    • Hide
      1. Run WildFly with attached configuration
      2. Run cli:
        /subsystem=xts:write-attribute(name=async-registration, value=${env.var:false})
        :reload
        
      Show
      Run WildFly with attached configuration Run cli: /subsystem=xts:write-attribute(name=async-registration, value=${env. var : false }) :reload
    • Undefined
    • ---
    • ---

    Description

      XTS subsystem supports expression for async-registration as described in the description:

      /subsystem=xts:read-resource-description
      ...
              "attributes" => {
                  "async-registration" => {
                      "type" => BOOLEAN,
                      "description" => "Initialize endpoints for asynchronous registration needed for WS-AT .NET integration.",
                      "expressions-allowed" => true,
                      "required" => false,
                      "nillable" => true,
                      "default" => false,
                      "access-type" => "read-write",
                      "storage" => "configuration",
                      "restart-required" => "all-services"
                  },
      

      However if I set the attribute to an expression, the server fails to reload:

      12:17:26,482 ERROR [org.jboss.as.controller] (Controller Boot Thread) 
      
      OPVDX001: Validation error in standalone-xts.xml -------------------------------
      |
      |  670:         <xts-environment url="http://${jboss.bind.address:127.0.0.1}:8080/ws-c11/ActivationService"/>
      |  671:         <default-context-propagation enabled="true"/>
      |  672:         <async-registration enabled="${env.var:false}"/>
      |                                   ^^^^ '${env.var:false}' isn't a valid value for the 'enabled' attribute
      |
      |  673:     </subsystem>
      |  674: </profile>
      |  675: <interfaces>
      |
      | The primary underlying error message was:
      | > ParseError at [row,col]:[672,13]
      | > Message: WFLYCTL0106: Invalid value '${env.var:false}' for attribute
      | >   'enabled'
      |
      |-------------------------------------------------------------------------------
      
      12:17:26,483 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
      	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
      	at org.jboss.as.server.ServerService.boot(ServerService.java:395)
      	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
      	at java.lang.Thread.run(Thread.java:748)
      
      12:17:26,484 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
      

      The subsystem is deprecated hence priority is major.

      "result" => {
              "description" => "The configuration of the XST subsystem.",
              "deprecated" => {
                  "since" => "3.0.0",
                  "reason" => "Deprecated since the XTS feature set is rarely used and is considered legacy within development approaches nowadays."
              },
      

      Attachments

        Activity

          People

            ochaloup@redhat.com Ondrej Chaloupka (Inactive)
            padamec@redhat.com Petr Adamec
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: