you end up in a primitive but interesting Web Application with plenty of documentation on all the MBeans available
Let alone the capacity to navigate and interrogate MBeans, the dms webapp is also valuable for all the documentation it provides (click on Metrics Definition)
For example the JVM_MemoryPool and the JVM_MemorySet bring valuable information on the JVM memory utilization :
JVM_MemoryPool
Name | Host | Process | memory_manager | type | usedAfterCollect, KB | usedNow, KB | usedPeak, KB | valid | JVM | JVM_Memory | ServerName |
---|---|---|---|---|---|---|---|---|---|---|---|
Code Cache | localhost | AdminServer:7009 | CodeCacheManager | Non-heap memory | 0 | 18555 | 18558 | TRUE | JVM | memory | AdminServer |
PS Eden Space | localhost | AdminServer:7009 | PS MarkSweep, PS Scavenge | Heap memory | 0 | 86964 | 526385 | TRUE | JVM | memory | AdminServer |
PS Old Gen | localhost | AdminServer:7009 | PS MarkSweep | Heap memory | 0 | 314223 | 314223 | TRUE | JVM | memory | AdminServer |
PS Perm Gen | localhost | AdminServer:7009 | PS MarkSweep | Non-heap memory | 0 | 290873 | 290873 | TRUE | JVM | memory | AdminServer |
PS Survivor Space | localhost | AdminServer:7009 | PS MarkSweep, PS Scavenge | Heap memory | 2671 | 2671 | 101035 | TRUE | JVM | memory | AdminServer |
Wed Jun 29 18:26:46 CEST 2011
Copyright © 2002, 2009, Oracle and/or its affiliates. All rights reserved.
JVM_MemorySet
Name | Host | Process | committed, KB | init, KB | max, KB | used, KB | JVM | JVM_Memory | ServerName |
---|---|---|---|---|---|---|---|---|---|
Heap memory | localhost | AdminServer:7009 | 1230528 | 1048576 | 1864192 | 396667 | JVM | memory | AdminServer |
Non-heap memory | localhost | AdminServer:7009 | 302464 | 133568 | 573440 | 302196 | JVM | memory | AdminServer |
No comments:
Post a Comment