mod_cluster load metric capacity and weight defaults are wrong -------------------------------------------------------------- Key: AS7-1647 URL: https://issues.jboss.org/browse/AS7-1647 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.0.2.Final, 7.1.0.Beta1 The context of the capacity of a load metric is metric-specific. The default capacity values should be defined per-metric, or at least default to 1. Also, the weight of a metric should default to 1, not 9. Additionally, the defaults for load history should default to something reasonable (e.g. 10), not 512; same for decay factor (2, instead of 512). Also, capacity should expect a double, not an integer. This is important, since many load metrics represent their load values as decimal values between 0 and 1.

mod_cluster load metric capacity and weight defaults are wrong -------------------------------------------------------------- Key: AS7-1647 URL: https://issues.jboss.org/browse/AS7-1647 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.0.2.Final, 7.1.0.Beta1 The context of the capacity of a load metric is metric-specific. The default capacity values should be defined per-metric, or at least default to 1. Also, the weight of a metric should default to 1, not 9. Additionally, the defaults for load history should default to something reasonable (e.g. 10), not 512; same for decay factor (2, instead of 512). Also, capacity should expect a double, not an integer. This is important, since many load metrics represent their load values as decimal values between 0 and 1.