Bug 862897 - [RFE] Make VM Health check thread more verbose
Summary: [RFE] Make VM Health check thread more verbose
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Agent
Version: JON 3.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-03 20:29 UTC by Charles Crouch
Modified: 2015-02-01 23:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-05 19:41:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 34192 0 None None None 2012-10-03 20:30:22 UTC

Description Charles Crouch 2012-10-03 20:29:36 UTC
Right now the VM Health check thread, when it sees high memory utilization, will log a message saying roughly: "Too much memory being consumed: XXX Mb"

It would be helpful if we could log more information to get an idea about what exactly is consuming all of the memory. A quick google shows information on memory per thread doesn't look very promising, perhaps we could just log the values from the java.lang.MemoryPool jvm mbeans?
If we wanted to get fancier we could perhaps look at some of the hooks things like 
http://visualvm.java.net/index.html (does jdk7 help here?) or Thermostat (http://icedtea.classpath.org/wiki/Thermostat#Memory_Management) are using?

Comment 1 Jay Shaughnessy 2014-08-25 20:17:02 UTC
Recommend close or JON4.

Comment 2 Larry O'Leary 2015-01-05 19:41:31 UTC
Closing this as no progress has been made in this area.

As of the JBoss ON 3.3 release, the VM health check thread is still unable to inform the user or administrator of VM health issues.


Note You need to log in before you can comment on or make changes to this bug.