[jboss-jira] [JBoss JIRA] (WFLY-10834) Load provider settings is not taken into account in mod_cluster subsystem

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated WFLY-10834:
----------------------------------
    Priority: Blocker  (was: Critical)


> Load provider settings is not taken into account in mod_cluster subsystem
> -------------------------------------------------------------------------
>
>                 Key: WFLY-10834
>                 URL: https://issues.jboss.org/browse/WFLY-10834
>             Project: WildFly
>          Issue Type: Bug
>          Components: mod_cluster
>    Affects Versions: No Release
>         Environment: Latest nightly from ci.wildfly.org
>            Reporter: Jan Kašík
>            Assignee: Radoslav Husar
>            Priority: Blocker
>             Fix For: 14.0.0.CR1
>
>
> Everything works in version with old subsytem with this settings (load is properly reported to balancer):
> {code:xml}
> <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>
> {code}
> Same configuration for latest snapshot doesn't work (load remains at 1):
> {code:xml}
> <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>
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)