[
https://issues.jboss.org/browse/AS7-1764?page=com.atlassian.jira.plugin.s...
]
Michal Babacek updated AS7-1764:
--------------------------------
Description:
h3. The current state
The following load metrics return *Load: 100* regardless the actual load being generated:
* *requests*
* *sessions*
whereas these metrics appear to *work correctly*:
* *cpu*
* *mem*
(For the aforementioned abbreviations please consult [Mod_cluster 1.1.x
docs|http://docs.jboss.org/mod_cluster/1.1.0/html_single/])
According to my opinion, it looks like the *Web Container metrics*, unlike the *System/JVM
metrics*, do not work.
(i) *Note:* Load metric attributes, such as *capacity*, were correctly set and verified
with the [
documentation|http://docs.jboss.org/mod_cluster/1.1.0/html_single/] and
["Interview with
Paul"|https://docspace.corp.redhat.com/docs/DOC-73684] on
mind.
h3. Previous JIRAs
* There is [JBPAPP-7077] saying, that "Dynamic-load-provider returns Load:1
regardless of load-metric set". This is no longer truth, likely thanks to [AS7-1648].
If you set either *requests* or *sessions* metric with Dynamic-load-provider, you shall
get *Load: 100* all the time. Last but not least, *cpu* and *mem* metrics work properly
now.
was:
h3. The current state
The following load metrics return *Load: 100* regardless the actual load being generated:
* *requests*
* *sessions*
whereas these metrics appear to *work correctly*:
* *cpu*
* *mem*
(For the aforementioned abbreviations please consult [Mod_cluster 1.1.x
docs|http://docs.jboss.org/mod_cluster/1.1.0/html_single/])
According to my opinion, it looks like the *Web Container metrics*, unlike the *System/JVM
metrics*, do not work.
(i) *Note:* Load metric attributes such as *capacity* was correctly set and verified with
[
documentation|http://docs.jboss.org/mod_cluster/1.1.0/html_single/] and ["Interview
with
Paul"|https://docspace.corp.redhat.com/docs/DOC-73684] on mind.
h3. Previous JIRAs
* There is [JBPAPP-7077] saying, that "Dynamic-load-provider returns Load:1
regardless of load-metric set". This is no longer truth, likely thanks to [AS7-1648].
If you set either *requests* or *sessions* metric with Dynamic-load-provider, you shall
get *Load: 100* all the time. Last but not least, *cpu* and *mem* metrics work properly
now.
Web Container metrics do not work and System/JVM metrics do
-----------------------------------------------------------
Key: AS7-1764
URL:
https://issues.jboss.org/browse/AS7-1764
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Environment: Httpd:mod_cluster-1.1.3.Final-linux2-x86_64.zip,
AS:jboss-as-7.1.0.Alpha1-SNAPSHOT-e4519ab.zip (master)
Reporter: Michal Babacek
Assignee: Paul Ferraro
Labels: mod_cluster
h3. The current state
The following load metrics return *Load: 100* regardless the actual load being
generated:
* *requests*
* *sessions*
whereas these metrics appear to *work correctly*:
* *cpu*
* *mem*
(For the aforementioned abbreviations please consult [Mod_cluster 1.1.x
docs|http://docs.jboss.org/mod_cluster/1.1.0/html_single/])
According to my opinion, it looks like the *Web Container metrics*, unlike the
*System/JVM metrics*, do not work.
(i) *Note:* Load metric attributes, such as *capacity*, were correctly set and verified
with the [
documentation|http://docs.jboss.org/mod_cluster/1.1.0/html_single/] and
["Interview with
Paul"|https://docspace.corp.redhat.com/docs/DOC-73684] on
mind.
h3. Previous JIRAs
* There is [JBPAPP-7077] saying, that "Dynamic-load-provider returns Load:1
regardless of load-metric set". This is no longer truth, likely thanks to [AS7-1648].
If you set either *requests* or *sessions* metric with Dynamic-load-provider, you shall
get *Load: 100* all the time. Last but not least, *cpu* and *mem* metrics work properly
now.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira