Details
-
Type:
Sub-task
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 1000
-
Component/s: Runtime: JMX
-
Labels:None
-
Number of attachments :
Description
The easiest way to make a start on implementing the JMX beans is to fulfill the VM interfaces for the relatively simple beans. These are the runtime, class loading and compilation beans.
Most of these can be fulfilled by probing existing RVM properties or calling existing methods. The main issues are:
- Recording and returning the start time of the VM
- Recording and returning the number of classes loaded/unloaded
- Recording and returning the amount of time spent compiling
Activity
Andrew John Hughes
logged work - 15/Jul/07 6:52 PM
-
- Time Spent:
- 1 hour
-
The monitoring of class loading has been added (although we don't check for unloading -- need to know if these even exists).
For compiler, need to know how to deal with the possibility of one of three being invoked; which one should we report on? Stats are already available from org.jikesrvm.compiler.common.VM_RuntimeCompiler
Need to find out how to retrieve command-line arguments
Need to make accessible boot time in VM_Time
Andrew John Hughes
logged work - 05/Aug/07 10:08 AM
-
- Time Spent:
- 5 hours
-
Initial versions of all three beans are now committed:
* Runtime bean pulls data from new methods in VM_Time and VM_CommandLineArgs
* Compilation bean pulls timing data from VM_RuntimeCompiler if monitoring is turned on by the command line option -X:vm:measureCompilation=true
* Class loading is monitored. There is currently no class unloading so 0 is returned.
We need to consider further what to return for getName() as part of the runtime bean. At present, this is just a generic string but it should really be something instance specific. Sun return PID@hostname.
