-
Sub-task
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
None
skitt and I had a discussion today how to best proceed on the parent issue, and AFTER the other two sub tasks have been clarified, would like to see more details about the evolution of both heap and native memory usage of this JVM in this scenario.
There are a couple of ways this could be obtained:
- using a JMX client such as VisualVM or Java Mission Control
- using Apache Karaf Decanter, need
INTDIST-95 - using collectd, see e.g. Sai's blog ?
- using some custom ODL code that just logs - I'll try something in infrautils, see
INFRAUTILS-19andINFRAUTILS-20
- is blocked by
-
INTDIST-95 unable to add apache decanter repo in nitrogen distribution
- Resolved
-
INFRAUTILS-20 Monitorability of JVM's native memory usage
- Resolved