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

Load provider settings is not taken into account in mod_cluster subsystem

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: No Release
    • Fix Version/s: 14.0.0.Beta2
    • Component/s: mod_cluster
    • Labels:
      None
    • Environment:

      Latest nightly from ci.wildfly.org

      Description

      Everything works in version with old subsytem with this settings (load is properly reported to balancer):

      <subsystem
      	xmlns="urn:jboss:domain:modcluster:3.0">
      	<mod-cluster-config advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
      		<dynamic-load-provider>
      			<load-metric type="cpu"/>
      		</dynamic-load-provider>
      	</mod-cluster-config>
      </subsystem>
      

      Same configuration for latest snapshot doesn't work (load remains at 1):

      <subsystem
      	xmlns="urn:jboss:domain:modcluster:4.0">
      	<proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" connector="ajp">
      		<dynamic-load-provider>
      			<load-metric type="cpu" weight="1"/>
      		</dynamic-load-provider>
      	</proxy>
      </subsystem>
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rhusar Radoslav Husar
                Reporter:
                jkasik Jan Kasik
                Tester:
                Jan Kasik
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: