[
https://jira.jboss.org/jira/browse/JBAS-6832?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6832:
---------------------------------
Summary: JBoss AS JVM Metrics stay the same through the console (was: JBoss AS
node: JVM Metrics stay the same)
Component/s: ProfileService
Fix Version/s: JBossAS-5.1.0.GA
Assignee: Scott M Stark (was: Ondrej Žižka)
On the console side we don't treat JVM metrics any different to any others, e.g. the
JBM destination metrics which Farah has seen getting updated. So I think its worth
investigating this on the JBAS side to see if the JBAS server JVM stats are configured
correctly.
JBoss AS JVM Metrics stay the same through the console
-------------------------------------------------------
Key: JBAS-6832
URL:
https://jira.jboss.org/jira/browse/JBAS-6832
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Environment: EmbJopr (r329)
Reporter: Ondrej Žižka
Assignee: Scott M Stark
Fix For: JBossAS-5.1.0.GA
JVM metrics in the JBoss AS node, Summary tab, stay the same whatever I do.
To test, I've tried to allocate some memory (5 MB) in JSFUnit tests.
In manual tests, I've opened about 25 links at once in JMX console.
Metrics data didn't change a bit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira