Default mod_cluster load metric cpu (AverageSystemLoadMetric) is not supported on Windows ----------------------------------------------------------------------------------------- Key: WFLY-5890 URL: https://issues.jboss.org/browse/WFLY-5890 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR5 Reporter: Michal Karm Babacek Assignee: Radoslav Husar Priority: Critical Labels: ux h3. Problem Wildfly 10's default load metric changed from *busyness* to *cpu*. Although otherwise fine, this change has a one major drawback: It doesn't work on Windows JDKs: MODCLUSTER-234. This fact has been known and acknowledged since 2011. {code} <subsystem xmlns="urn:jboss:domain:modcluster:2.0"> <mod-cluster-config advertise-socket="modcluster" connector="ajp"> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> {code} Instead of a valid Load value, subsystem returns 0 and prints: {{MODCLUSTER000045: AverageSystemLoadMetric is not supported on this system and will be disabled.}} h3. Example {code} C:\Users\Administrator>groovy https://gist.githubusercontent.com/Karm/be36292ae52ded419b46/raw/addd6abf... load: -1.0 avail. processors: 4 {code} {code} mbabacek@localhost:~$ groovy https://gist.githubusercontent.com/Karm/be36292ae52ded419b46/raw/addd6abf... load: 0.67 avail. processors: 4 {code} h3. Call to action IMHO, this is a Major user experience failure, the default should provide meaningful values on all major platforms.