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

mod_cluster custom load metrics fail to load

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Critical
    • Resolution: Done
    • 7.2.0.Beta
    • 7.2.0.CD14
    • mod_cluster
    • None
      1. Start Wildfly
      2. Add custom load metrics with 'module' defined
      3. Reload
    • Workaround Exists
    • Hide
      1. Add custom load metric module as a resource to org.wildfly.extension.mod_cluster module:
        <resources>
            <resource-root path="mod_cluster-custom-metric.jar"/>
            <resource-root path="wildfly-mod_cluster-extension-[version].jar"/>
        </resources>
        
      2. Add <module name="org.jboss.as.server"/> as a dependency to org.wildfly.extension.mod_cluster module
      3. Restart server
      Show
      Add custom load metric module as a resource to org.wildfly.extension.mod_cluster module: <resources> <resource-root path= "mod_cluster-custom-metric.jar" /> <resource-root path= "wildfly-mod_cluster-extension-[version].jar" /> </resources> Add <module name="org.jboss.as.server"/> as a dependency to org.wildfly.extension.mod_cluster module Restart server
    • User Experience

    Description

      This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.

      OPVDX001: Validation error in standalone-ha.xml --------------------------------
      |
      |  448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
      |  449:     <dynamic-load-provider>
      |  450:         <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
      |                                                                                 ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
      |                                                                                        element
      |
      |                                                                                      Attributes allowed here are: capacity, class, module, weight
      |
      |  451:             <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
      |  452:             <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
      |  453:         </custom-load-metric>
      |
      | 'module' is allowed on elements:
      | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
      | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
      | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
      | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
      | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
      | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
      | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
      | - server > extensions > extension
      | - server > vault
      | - server > management > security-realms > security-realm > plug-ins > plug-in
      | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
      | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
      | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
      | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
      | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
      | (and 26 more)
      |
      | The primary underlying error message was:
      | > ParseError at [row,col]:[450,21]
      

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Jan Kasik Jan Kasik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: